Requests & responses

Base URL

https://api.illyvoip.com

Use the method and complete path documented for each operation. API endpoint paths currently use /api/v1/. A portal release name and an API path version are separate concepts.

Request formats

Follow each endpoint’s content type. Many writes use JSON; transcription accepts multipart form data. For multipart requests, let your HTTP library set the boundary. Do not send a JSON body where a file upload is required.

Pagination

Pagination is endpoint-specific. Call History uses limit and an opaque cursor. Follow pagination.next_cursor while pagination.has_more is true. Other lists may use numbered pages. Use the exact fields documented on that operation.

Acceptance and completion

Read HTTP status, the response body and resource state together. A queued SMS is not yet delivered; an accepted call request is not necessarily answered. Use status endpoints and webhook events to follow the operation.

Examples and prices

Example IDs, numbers, timestamps and monetary amounts illustrate the data format. Obtain current prices through the relevant quote or pricing operation. A number in a sample response is not a live offer.

Speech and lookup billing

The portal reference reviewed on 9 October 2026 lists these rates. Confirm current account pricing before sending requests; this dated reference is not a price guarantee.

• Speech-to-text: €0.0350 per started minute.
• Text-to-speech: €0.000050 per character (€0.0500 per 1,000 characters).
• Voice API gather and speak use the same STT/TTS rates.
• The portal separately lists AI Voice Agent usage at €0.1200 per started minute; this does not imply an AI-agent endpoint in the HTTP specification.
• Standard live HLR: €0.0125. A returned porting date adds €0.0125.
• Supported UK/Ireland fixed-line activity and supported US mobile activity: €0.0250 total. Supported US mobile activity with a returned porting date: €0.0375 total.

The lookup response’s cost_eur reports the amount billed for that request. See the operation reference for supported options and conditions.

Sandbox testing

Use the separate Sandbox environment and scenario reference for simulated responses and its own API key. Do not send sandbox scenario headers to production.

Production requests

The examples target the production API. Calls, messages, number orders and other operations can incur charges or change account data. Reading this documentation does not submit requests.