Developers

Developer documentation

Send WhatsApp messages, place voice calls, connect your team to customers with click to call, have an AI voice agent call your customers, verify customers over a call and receive signed events, all from your own code.

WhatsApp base URL
https://app.agentive.co.in/api/v1
Voice base URL
https://api.agentive.co.in/api/public/v1
Webhook payload version
2026-06-01

The earlier Voice base URL https://voice.agentive.co.in/api/public/v1 keeps working too, with the same keys and the same answers.

Products

Every reference has authentication, request and response shapes, error codes and copy-ready samples.

OpenAPI specification

Getting started

Three steps from a new account to a live request.

  1. 1

    Sign in to your account

    The WhatsApp API is issued from the Chat dashboard and the voice APIs from the Voice dashboard, so start with the product you are integrating.

  2. 2

    Get your credentials

    Generate credentials in the dashboard. Each reference explains where to find them and which headers to send on every request.

  3. 3

    Make your first request

    Copy the quick start for your product, replace the placeholders, and send one message or place one call to your own number.

Platform conventions

Agentive ships two API families: the Voice APIs (Voice Broadcast, Click to Call, AI Voice Agent, Voice OTP and telephony webhooks) and the WhatsApp Business API. They share a brand, a dashboard account and a set of habits, but they are separate products and they do not agree on everything. This section is the one place that says what is common and, where they differ, exactly how.

Base URLs

Voice APIsWhatsApp Business API
Base URLhttps://api.agentive.co.in/api/public/v1, the API's own host since 17 October 2026. https://voice.agentive.co.in/api/public/v1 keeps working with the same keys and the same answers.https://app.agentive.co.in/api/v1
CoversVoice Broadcast, Click to Call, AI Voice Agent, Voice OTP and the endpoints webhook events point back at. All of them share one base, one credential pair and one envelope.Template sends for one API campaign. Issued and managed from the Chat dashboard.
TransportHTTPS only, JSON in and JSON out. Since 17 October 2026 api.agentive.co.in refuses plain HTTP with 403 https_required and never redirects it; voice.agentive.co.in redirects it, after the request has already crossed the network in clear.HTTPS only, JSON in and JSON out.

Authentication

Voice APIsWhatsApp Business API
CredentialOne publishable key (pk_live_...) and one secret (sk_live_...) per account.One token (agcamp_...) per API campaign, so a leaked token can only send that campaign.
How to send itx-api-key and x-api-secret headers, or HTTP Basic with the publishable key as the username and the secret as the password. A secret field in the JSON body is refused by the click to call endpoints and deprecated on the others (since 17 October 2026).Authorization: Bearer <token>.
ScopeAccount-wide. Every endpoint on the Voice base accepts it. A key can carry a list of allowed addresses; see Security below.Campaign-wide. The template and number are fixed on the campaign.
Treat asBoth keys are confidential. The publishable key names your account to anyone who holds it, so keep it with the secret, on your server only.A secret. Keep it on your server only.
RotationFrom the API Access tab of the Voice dashboard. By default the old secret stops working at once; for a planned change you can keep it working for 24 hours beside the new one.From the campaign page in the Chat dashboard. The old token stops working at once.

Error envelope

Voice APIsWhatsApp Business API
Shape{ status, code: number, error_code: string, error, details, unique_id, reference_id }{ error, code: string, details: object }
What to branch onerror_code. The numeric code mirrors the HTTP status and stays for compatibility.code, which is itself the machine string.
Human sentencedetails, repeated in error so a handler written for the WhatsApp shape reads a Voice error too.error.
Extra contextNamed fields beside the envelope (lines, lines_in_use, attempts_left, retry_after_sec, balance_inr).A details object (missing, retryAfter, meta, validation).

401 and 403

Voice APIsWhatsApp Business API
401Credentials missing, unknown, or rejected. The status never confirms whether a key exists.Token missing or wrong.
403Credentials accepted, but the account is not active or the product is not enabled. Also when the key's address list does not include the calling address (ip_not_allowed, once address lists are checked), and for plain HTTP to api.agentive.co.in (https_required, since 17 October 2026). A key whose account is not active, or whose API access is not enabled, is limited on its own: 240 of those refusals a minute, then HTTP 429 rate_limited with a Retry-After.Token accepted, but the campaign is not live or the number is not connected.
404Not found, or not yours. A foreign id is never a 403, because that would confirm it exists.Not found, or not yours. Same rule.

Idempotency

Voice APIsWhatsApp Business API
KeyIdempotency-Key request header, 1 to 128 visible characters. A longer key is refused with HTTP 400.externalId in the body (the Idempotency-Key header is accepted too), up to 160 characters.
Window24 hours per account.The life of the campaign.
A repeatReplays the stored response. The one exception is a 5xx raised after the call was already handed to the network: that reply is stored as call_state_unknown with a sentence appended telling you to check the call before retrying. A 400 or 404 is stored for the 24 hours too, so once you fix the request or the dashboard setting, send it with a new key. A 401 is never stored: the credentials are checked before the key is read.HTTP 200 with duplicate: true and the earlier delivery's current status.
Replay markerIdempotent-Replayed: true, plus the original idempotency-replayed: true header.duplicate: true in the body.
Same key, different bodyHTTP 422 with idempotency_conflict.The first send stands; the second is reported as a duplicate.
Still in flightHTTP 409 with idempotency_in_progress and Retry-After.Not applicable.

Rate limits and headers

Voice APIsWhatsApp Business API
BudgetPer account: 120 reads a minute and 120 writes a minute, counted separately, so polling can never starve call placement. Recording and voicemail downloads have their own 120 a minute. Since 17 October 2026 click to call controls have their own 120 a minute too, MP3 or WAV downloads and creating a recording link count in the download budget, and playing a recording link has its own budget of 600 a minute per account. Before keys are checked, requests are also limited by where they come from, counting only requests whose keys are rejected: 240 a minute per client address and 2,400 a minute per network address; going over answers HTTP 429 rate_limited with a Retry-After. Since 17 October 2026 a request with valid keys is not refused because of other callers' rejected requests, except while one network address is sending more than 24,000 rejected requests a minute.Per campaign token: 300 requests a minute over a sliding window.
Limit headersRateLimit-Limit, RateLimit-Remaining and RateLimit-Reset, with X-RateLimit-* aliases of the same three values.None.
How long to waitRetry-After on every 429 and every 409, mirrored in the body as retry_after_sec.Retry-After on rate_limited; details.retryAfter (IST) on quiet_hours.
Capacity refusalPlace a call, Trigger a saved campaign, Send a verification code and Place an AI agent call answer HTTP 429 concurrency_limit when the account has no free line, with lines, lines_in_use and retry_after_sec in the body and a Retry-After of 5 seconds. Call-placing responses also carry X-Agentive-Lines and X-Agentive-Lines-In-Use. Since 17 October 2026 a call your team members place over the internet (the dashboard, the apps, a click to call) counts against the lines too, and a call you place with Place a call, Trigger a saved campaign or Send a verification code holds its line until its call exists, up to 60 seconds (before, 3 seconds); an AI voice agent call (Place an AI agent call, or the trigger of an AI voice agent campaign) still frees its line 3 seconds after the request. A click to call takes its line before the team member is rung (two lines on Phone Bridge, one over the internet); when none is free it answers concurrency_limit with retry_after_sec 30 and a Retry-After of 30 seconds, without the lines figures or the X-Agentive-Lines headers.Not applicable; there are no lines to exhaust.

Webhook signing

Voice APIsWhatsApp Business API
Header to verifyX-Agentive-Signature-V2: t=<unix seconds>,v2=<hex>X-Agentive-Signature: <hex>, with no prefix.
What is signedHMAC-SHA256, with the signing secret, of t, a dot, then the exact raw body.HMAC-SHA256 of the exact raw body with the endpoint's signing secret.
FreshnessReject a t more than 300 seconds from your own clock. The timestamp is inside the signed material, so a captured delivery cannot be sent again later.Nothing time-bound is signed. De-duplicate on the event id for good, and accept deliveries over HTTPS only.
ComparisonConstant time, on bytes. Reject on any mismatch, and reject a delivery with no version 2 header.Constant time, on bytes. Reject on any mismatch.
Two different signatures
The Voice APIs sign the timestamp together with the body, and you verify only X-Agentive-Signature-V2. Voice deliveries also carry the older body-only X-Agentive-Signature for receivers built before version 2; do not accept it on its own, because it proves nothing about when a body was sent. The WhatsApp signature is the body alone with no prefix. A shared handler needs one verifier per product.

Webhook delivery headers

Voice APIsWhatsApp Business API
Event nameX-Agentive-EventX-Agentive-Event
Event idX-Agentive-Event-Id, the same value as id in the body. Shared by every endpoint that receives the event.X-Agentive-Delivery, the same value as id in the body. Despite the name it is the event id, not a per-endpoint delivery id.
Delivery idX-Agentive-Delivery-Id (dlv_...), one per event per endpoint, stable across every retry.None. X-Agentive-Delivery is the Chat product's name for the event id above.
Attempt numberX-Agentive-Attempt, 1-based, counting through the whole retry schedule.None.
Attempt timeX-Agentive-Timestamp, Unix seconds at the moment of this attempt, the same value as t in the version 2 signature. Check the age against the signed t, never against this header alone.X-Agentive-Timestamp, the same timestamp as the envelope.
User agentAgentive-Webhooks/2026-06-01Agentive-Webhooks/2026-05-08, the Chat payload version.
Sent fromOne IPv4 address, 139.59.48.158, since 17 October 2026, for endpoint events, campaign and key press webhooks, and your AI voice agent's webhooks (one narrow exception is in Where webhooks come from). We will tell you at least 30 days before it changes, by email to your account admins and in these docs. Still verify the signature.No published address. Verify the signature.

Webhook retries

Voice APIsWhatsApp Business API
AttemptsNine: three fast, then six spread out.Three.
Schedule0.5 s and 2 s between the first three, then 1 min, 5 min, 30 min, 2 h, 6 h and 12 h.0 s, 2 s and 8 s.
Total windowAbout 20 hours. A delivery not accepted 21 hours after its event is not sent again: it is marked failed when its next attempt comes due. Since 17 October 2026, while an endpoint is failing, we send one waiting delivery at a time, oldest first, and hold the rest; once it accepts one again, the held deliveries already due follow a few at a time. A held delivery can therefore reach its later attempts later than the schedule above.About 10 seconds.
Timeout per attempt6 seconds.10 seconds.
What you seeThe dashboard lists the latest 50 deliveries per endpoint with the event, the latest result, the number of tries and the time in IST. Each delivery is kept for 30 days, then deleted.The campaign's Deliveries tab shows the message and its current status.

Timestamps and amounts

Voice APIsWhatsApp Business API
Time zoneIndian Standard Time, ISO 8601 with a +05:30 offset. The field is named per product: created_at_ist on a call, expires_at_ist on a verification, timestamp_ist on a webhook envelope.timestamp on the webhook envelope is UTC ISO 8601. Schedules and quiet hours are set and reported in IST.
UTC alongsidecreated_at_utc on a call, and occurred_at (UTC) plus created (Unix seconds) on a webhook envelope.The envelope timestamp is already UTC.
MoneyIndian Rupees, always. balance_inr is a number, never a formatted string.Indian Rupees, always. Amounts appear in the dashboard, not in the send API.

Versioning and field case

Voice APIsWhatsApp Business API
API versionIn the path: /api/public/v1.In the path: /api/v1.
Payload versionapi_version on every webhook event. Currently 2026-06-01.apiVersion on every webhook event. Currently 2026-05-08.
CompatibilityFields are added, never removed or redefined. Ignore fields you do not recognise.Fields are added, never removed or redefined. Ignore fields you do not recognise.
Field casesnake_case throughout, request and response.camelCase throughout, request and response.

Security

  • Every credential is a secret. That includes the Voice publishable key, whatever its name suggests: treat it exactly like the secret. Keep all keys on your server, in an environment variable or a secrets store, never in a browser, a mobile app, a spreadsheet or source control.
  • Send them only to the API. Never forward a key or a secret to any other host, and do not let an HTTP client carry them across a redirect to another host.
  • Rotate at once if one leaks. Rotate the Voice pair from the API Access tab of the Voice dashboard and a WhatsApp token from its campaign page. A leaked value must stop working immediately, so update your server in the same step. (For a planned Voice change, and only then, you can keep the old secret working for 24 hours.)
  • HTTPS only. Write https:// in the base URL in your code. A request sent over plain HTTP has already exposed its credentials before any redirect can protect it. Since 17 October 2026 api.agentive.co.in refuses plain HTTP with 403 https_required; if a secret was ever sent over plain HTTP, rotate it.
  • Restrict a key to your servers. Since 17 October 2026 a Voice key can carry up to 10 allowed addresses or ranges, set under Allowed addresses on the API Access tab. A list takes effect once address lists are checked: until then the card says address lists are not being checked and the key is accepted from any address. Use api.agentive.co.in when your key has a list: there we see your server's own address exactly. api.agentive.co.in has an IPv4 address only: list your server's public IPv4 address. See Restrict your key to your servers' addresses.
  • Webhooks come from one address. Since 17 October 2026 our webhooks (endpoint events, campaign and key press webhooks, and your AI voice agent's webhooks) are sent from 139.59.48.158 (IPv4 only), and we will tell you at least 30 days before it changes, by email to your account admins. Allow it on your firewall if you need to, but the address says where a request came from, not that it is ours: authenticate every webhook by its signature. See Where webhooks come from for the one narrow exception.
Report a vulnerability
If you find a security problem in the APIs, the webhooks or the dashboard, write to hello@agentive.co.in with the steps to reproduce it. Please do not test against accounts that are not yours. Our contact details are also published at /.well-known/security.txt.
Reading this as one platform
The habits that hold across both products: HTTPS only, JSON both ways, a stable machine code on every error, an idempotency key on every request a retry could repeat, HMAC-SHA256 on every webhook, Indian Rupees and Indian Standard Time. The habits that do not: the credential header, the envelope key names, the field case, the signature scheme and the retry schedule. Write one transport layer per product, then share everything above it.

Changelog

Changes that could affect code you have already written. Everything not listed here is additive: new fields, new headers and new optional request fields, which a handler that ignores what it does not recognise absorbs on its own.

11 November 2026: a declined ring all reads declined; call menus skip a member nothing can ring

On a call menu key that rings its people all at once, a team member who declines in the dashboard or the app now reads declined in ring_attempts, with rang_sec the second they declined (rarely, the whole ring's length). Before, such an attempt could read the whole ring's result (stopped when the caller left, for example) and its length. Code that counts declines from ring_attempts now sees these. And call menus now skip a team member who shows Available but has nothing that could ring (no app, no open dashboard, no Phone Bridge): that attempt reads offline.

20 October 2026: calls placed from the Agentive CRM

Calls placed from the Agentive CRM are your team members' ordinary calls: they are not click to call sessions, so they never appear in GET /click-to-call and send no click_to_call events. Nothing changes in the answers your keys receive.

17 October 2026: the key secret in a request body, and only Indian numbers dialled

Two changes on every key. The details are in the OpenAPI document.

What changedIt used toIt nowWhat to do
The click to call routes refuse the key secret in the request bodyA secret field in the JSON body was read as the last resort on every POST, after the x-api-secret header and the HTTP Basic password.Since 17 October 2026 the click to call routes (/click-to-call, /members, /call-menus and everything under them) answer 400 validation_error on field secret to a body that carries it, even when the header is sent too. Every other POST still reads it, and its answer carries a Deprecation header.Send the secret in the x-api-secret header, or as the HTTP Basic password, on every route.
Only Indian numbers are dialledA number in a longer form, a number with another country code included, was cut to its last 10 digits and dialled: +44 7911 123456 rang 7911123456.Since 17 October 2026 POST /calls, POST /campaigns/{id}/trigger, POST /otp/send and POST /ai/calls refuse a number with another country code with 400 invalid_number ("Only Indian numbers can be called."), and a number with too many digits as an invalid number (validation_error on POST /ai/calls). POST /otp/verify by number refuses both with "A valid Indian mobile number is required."Send Indian mobile numbers in one of the accepted forms: 10 digits, 0 then 10 digits, 91 (or 91 0) then 10 digits, +91 (or +91 0) then 10 digits, or 0091 then 10 digits.

17 October 2026: answer times, lines, click to call, recordings, the API host, webhook address and new error codes

Eight changes on every key, except where a row says Telephony API. The details are in where webhooks come from, the Click to Call API, MP3 and WAV, recording links, the base URL, restricting your key to your addresses and the OpenAPI document.

What changedIt used toIt nowWhat to do
On a broadcast call a key press connected to a team member, answered_at is the team member's pickup (Telephony API)answered_at was the customer's answer to the broadcast (between 14 and 17 October 2026).Since 17 October 2026 answered_at is when the team member on the web panel or the app picked up, so the message, the key press and the team member's ring count in wait_sec, and talk_sec is the conversation. call.answered still carries the customer's answer; the terminal event carries the pickup, or a call.updated with changed answer (to an endpoint that ticks call.updated) when the pickup is recorded after the terminal event was sent. The started_at of the call's own recording file reads the customer's answer instead, worked out from the call's end and the file's length, so up to about a second before its first sound (such a call that was transferred keeps answered_at). A team member who takes such a call on their own mobile leaves the customer's answer.Apply events by version, and read talk_sec for the conversation.
Webhooks come from one addressNo fixed source address was published.Since 17 October 2026 our webhooks come from one IPv4 address, 139.59.48.158: the endpoint events (a test event sent from the dashboard included), campaign webhooks, the call menu key press webhook, and your AI voice agent's own webhook and its call events. Webhooks are sent over IPv4 only. One exception: an endpoint whose own address is between 159.89.160.0 and 159.89.175.255 (the network block our server sits in) receives deliveries from 159.89.167.255 instead. We will tell you at least 30 days before this address changes, by email to your account admins and in the reference. If we cannot send from it for a while, we do not switch to another address: endpoint events wait and are retried for up to 21 hours.If your firewall accepts HTTPS only from known sources, allow this address on the port your endpoint uses (443 or 8443). Keep verifying X-Agentive-Signature-V2: the address says where a request came from, not that it is ours.
Your team members' own calls count against your linesOnly a team member's Phone Bridge calls (two lines) and Call via SIM calls (one line) counted. A Phone Bridge click to call counted one line when it was placed, and a click to call over the internet was not counted. A call you placed through the API held its line for 3 seconds after the request.Since 17 October 2026 a call a team member places over the internet (the dashboard, the apps, a click to call) counts too. A click to call takes its line before the team member is rung (two lines on Phone Bridge, one over the internet) and keeps it until the call ends; when every line is in use it is refused with 429 concurrency_limit and Retry-After 30 seconds. A call you place with Place a call, Trigger a saved campaign or Send a verification code holds its line from the request until its call exists, up to 60 seconds; an AI voice agent call frees its line 3 seconds after the request, as before.Treat concurrency_limit as retryable after Retry-After. Read lines and lines_in_use from GET /account.
A click to call ring the member did not answer holds the next one (Telephony API)The 10-minute cooldown after 2 rings in a row the member did not answer counted missed and declined rings only.Since 17 October 2026 a ring cancelled before the member answered (by your hang up, or by us) counts too, and a ring the member did not answer holds the next click to call for that member for 15 seconds (429 member_cooldown, with Retry-After). A call the member answered never holds the next one.Wait for Retry-After, or call another member.
A click to call hang up waits for a transfer being placed, and an unhold checks the call (Telephony API)A hang up did not wait for a transfer of the call being placed. An unhold on a click to call that did not read on hold answered 200 without checking.Since 17 October 2026 a hang up sent while a transfer of the call is being placed waits for it, up to about 8 seconds: if the transfer went through, it answers with the click to call in state transferred and ends nothing; otherwise it ends the call; past that wait it answers service_unavailable (retry). After a hang up, every other control of the call answers call_ended (service_unavailable, retryable, while the hang up is still being carried out). An unhold on a click to call that does not read on hold checks the call: if hold music an API hold started still plays, it is stopped and the member's panel shows the call off hold, and it answers service_unavailable when that music cannot be stopped. A hold the member placed from their panel or app is left as it is: they take the call off hold there.Read the state a hang up answers: transferred means the call went on with the colleague. Retry service_unavailable.
Recordings and voicemails in MP3 or WAV, and 10-minute recording linksA download sent the file as stored (Ogg Opus for almost every call), and every download needed your keys.Since 17 October 2026 GET /calls/{id}/recording takes format=mp3 or format=wav and sends the recording converted, and so does GET /calls/{id}/voicemail for a message (Telephony API, with voicemail on your account). Without format you get the file as stored. POST /calls/{id}/recording-link creates a link that plays one recording (or one part of it, optionally as MP3 or WAV) without your keys, valid for at most 10 minutes; it needs call recording on your account and counts in the download budget.Nothing, unless you want MP3, WAV or a link. Treat a link like the recording itself: anyone who has it can play it until its expires_at.
The API has its own host, and a key can carry an address listThe API was reached at voice.agentive.co.in.Since 17 October 2026 the API has its own host, api.agentive.co.in (base URL https://api.agentive.co.in/api/public/v1), which answers only the API, only over HTTPS, and has an IPv4 address only. It refuses a plain HTTP request with 403 https_required and never redirects it. https://voice.agentive.co.in/api/public/v1 keeps working with the same keys and the same answers. You can also list up to 10 IPv4 or IPv6 addresses or ranges under Allowed addresses on the API tab. A list takes effect once we check address lists: until then your key is accepted from any address.Use api.agentive.co.in when your key has an address list: there we see your server's own address exactly. Never call either host over http://.
New error_code valuesThese seven codes were not answered.Added on 17 October 2026: recording_converting (503), conversion_failed (500), invalid_link (401), link_expired (403) and link_revoked (403) for downloads in MP3 or WAV and for recording links; https_required (403) for a plain HTTP request to api.agentive.co.in; ip_not_allowed (403) for a key with an address list, while address lists are checked.Handle an error_code you do not know by its HTTP status.

The list of error codes also holds network_busy (503, retryable true, Retry-After: 15): every line of the phone network your calling number uses is in use right now, so nothing was placed, no run was created and nobody was rung. Retry after the pause with the same Idempotency-Key. It can be answered by POST /calls, POST /campaigns/{id}/trigger, POST /otp/send, POST /ai/calls and POST /click-to-call: handle it like any retryable refusal.

17 October 2026: AI voice agent call limits, request body errors and the phone_bridge lane

Four more changes on every key, except where a row says Telephony API. The details are in limits on the call and the error codes.

What changedIt used toIt nowWhat to do
An AI voice agent call placed through the API has a time limit and stops before your balance runs outA call whose agent had no maximum call length set was given none, and a running call was not ended for your balance.Since 17 October 2026 an AI agent call placed with POST /ai/calls, or by triggering an AI agent campaign, ends after 20 minutes when its agent has no maximum call length set in your dashboard; an agent's own maximum always applies instead, with its time warning and its goodbye. It also ends with the agent's goodbye shortly before your balance can no longer pay for the AI agent calls running on your account; the most recent API call ends first. A call ended by either limit reads completed. Calls your customers make to your numbers and calls placed from your dashboard are never ended this way.Set a maximum call length on the agent if its calls need longer than 20 minutes, and keep your balance topped up.
An AI voice agent call needs a balance for every AI call already runningPOST /ai/calls needed a balance of at least ₹5, or the agent's price for one minute when that was higher.Since 17 October 2026 POST /ai/calls needs a balance of the agent's price for one minute for every AI agent call already running or being placed on your account, plus this one (at least ₹5), and answers 402 insufficient_balance naming the amount in minimum_balance_inr. Triggering an AI agent campaign needs the same, at least your account's AI per-minute rate.Treat 402 as top up and retry. Read minimum_balance_inr for the amount.
A request body we cannot read is answered in JSONA body that was not valid JSON, not in UTF-8, or compressed in a way we cannot read was answered with an HTML page.Since 17 October 2026 a body that is not valid JSON answers 400 with error_code validation_error, and a body that is not in UTF-8 or uses a Content-Encoding we cannot read answers 415 with error_code validation_error, both as JSON. The statuses are the same as before.Nothing, unless your code read the HTML page. Read error_code as on any other error.
A call that rang a team member's own mobile directly is found by lane=phone_bridge (Telephony API)An incoming call to your number that rang a team member's own mobile directly (not through a call menu) read lane phone_bridge on its record, but the lane filter of GET /calls found it under lane=direct.Since 17 October 2026 such a call is found by lane=phone_bridge, as its record reads. An earlier such call may still be found under lane=direct.Ask for lane=phone_bridge as well as lane=direct when you list calls by lane.

17 October 2026: a click to call's call menu record

One change to the click to calls your team member moves into a call menu, on every key. The details are in call and recording events.

What changedIt used toIt nowWhat to do
The call menu record of a click to call names the click to callWhen your team member moved a click to call into a call menu, the rest of the call went on as a record of its own (lane menu, named by the click to call's transfers[].to_call_id) with click_to_call_id, reference_id and metadata null and via_api false.Since 17 October 2026 that record carries the click to call's click_to_call_id, reference_id and metadata, and via_api true, on its events, its recording.available and every read; its unique_id stays its own. A call menu record from before then can show them on a read too, at its unchanged version; no event is sent again. With the Telephony API, GET /calls?click_to_call_id= returns it beside the click to call's own record, and so does ?reference_id= for the first 50 click to calls placed with that reference.If you match call events to a click to call by click_to_call_id, match on unique_id (the click to call id is the unique_id of its own record) and take the outcome from click_to_call.ended. Keep the call menu record's recording beside the click to call's own: it is the call menu part of the call.

15 October 2026: held time in recordings, and who ended the call

Two corrections to the calls your team handles. The recording change applies to every account; ended_by is read with the Telephony API and on the click to call object. The details are in the call object and who ended a click to call.

What changedIt used toIt nowWhat to do
A hold placed on a phone in the call is in the recording (every account)A hold placed on a phone in the call itself (the caller's or the customer's phone, or a team member's own mobile) was left out of the recording, so such a file could be shorter than the call by the time held. talk_sec already counted that time.Since 15 October 2026 the held time is in the recording, and in the recording's duration_sec. talk_sec counts it as before. hold_sec still counts only a hold placed from the panel, the apps or the API.Nothing.
Who ended the call: a team member's own mobile, and Live MonitorA call a team member answered on their own phone and hung up on it read ended_by null, and so did an outgoing Phone Bridge call they hung up. A call someone on your team ended from Live Monitor read null, or customer on a call answered in the app or browser. A click to call read the same way.An incoming call a team member answered on their own phone (through a call menu, a queue, ring without a menu or straight to them) reads member when they hung up on it, and so does an outgoing Phone Bridge call they hung up; a call their own phone network ended reads the same. A call someone on your team (an admin or manager) ended from Live Monitor reads member, and a call our support team ended reads system. The click to call object reads as its call does: a Phone Bridge click to call your team member hung up on their own mobile reads member, with end_reason member_ended. Some calls on a team member's own phone can still read null: Call via SIM, an outgoing Phone Bridge call the customer hung up, a campaign call connected to a team member's own mobile, or a call handed to a colleague's own mobile.Nothing.

14 October 2026: transfers, call menus, voicemail and click to call times

Corrections from our own end to end test of the Telephony API and the Click to Call API. They apply to the calls your team handles, on accounts with the Telephony API, except where a row says every account or every key. The details are in the call object, Telephony Webhooks and the click to call object.

What changedIt used toIt nowWhat to do
A call moved into a call menu goes on as a record of its own (every account)When your team member moved a click to call, or an outgoing call they placed, into a call menu, the call menu part read as answered at the move and sent call.answered then, whether or not anyone in the menu picked up, and nothing on the call it came from named that part. The first call's recording also ran on through the call menu part, so that part was stored twice.The call menu part is a record of its own, with its own call_id and unique_id, its own events and recording; with the Telephony API it reads lane menu, and the new transfers[].to_call_id on the call it came from names it. It reads ringing while the customer is in the menu and sends no call.ringing; its call.answered, and with the Telephony API its answered_at, come only when a team member picks up from the menu, or the number a menu key forwards the call to answers. One that a WhatsApp key, or a key that hands the call to an AI voice agent, connected ends call.completed with the move as its answered_at; one nobody answered ends call.no_answer. The first call's recording usually ends at the move. A click to call's click_to_call.ended stays its own outcome. An incoming call moved into a call menu keeps one record and one recording, as before. Not covered yet: a call your AI voice agent moves into a call menu still sends call.answered at the move.Do not read the move as an answer. With the Telephony API, follow transfers[].to_call_id to the rest of the call.
A call moved into a call menu sends its own terminal event sooner (every account)A call your team member moved into a call menu, where the rest of the call goes on as a record of its own, sent its terminal event only when the customer's whole call was over.It usually sends its terminal event a few seconds after the move, at the latest when the customer's whole call is over. The call menu's record sends its own terminal event when the customer's call ends.Nothing. The rest of the call is reported on the call menu's record.
Transferred calls: who answered, the whole conversation, the real endOur docs said that an outgoing call your team member transferred to a colleague who answered kept naming the member who placed it as member, and that member_id listed it under them. That was wrong in the docs only: the record already named the colleague. The call's duration_sec was only one member's part. A click to call transferred to a colleague who answered read ended_by api, or the word the click to call kept. A call handed to a colleague who did not answer ended at the transfer.Once a colleague answers a transferred call, outgoing or incoming, member names that colleague and member_id lists the call under them, as the record already did (on an outgoing call, call.answered names the member who placed it and the final event the colleague). An outgoing transferred call keeps the customer's answered_at, and its duration_sec (every account) is the whole conversation, both parts. A click to call transferred to a colleague who answered, through the API or from the panel or app, reads ended_by as the call then ended, or null; one you transferred through the API to a call menu, to an outside number, or to a colleague who did not answer, still reads api. A call handed to a colleague who did not answer ends when the caller's line ends: the colleague's ring and any goodbye or voicemail are in the record, so in talk_sec, and on a call menu call in duration_sec (every account).Apply events by version: member can change during a call. Calls you already received keep their version (no new event, no change feed entry): read a call again for the corrected ended_by. The answer, duration and end corrections apply to calls from this date; earlier records are not changed.
A call handed to a colleague reads live until it ends (every key)A call your team member handed to a colleague who took it in the dashboard or the app (including a transfer through the Click to Call API) read as ended at the transfer until the call's end was written.It reads status in_progress with end_reason null until the call itself ends, on reads and events for all keys; its terminal event then carries the end. With the Telephony API, ended_at reads null until then and version goes up at the end. A colleague who takes calls on their own mobile is not included: that record ends at the transfer.Treat a transferred call as over only at its terminal event, or when a read shows a terminal status.
A removed callback is not a callback madeA callback reminder your team removed, or moved to a newer reminder, read as done by the member who removed it.It reads callback_at, callback_done_at and callback_done_by null, and its call.tagged says so. A click to call's own disposition stays as it was saved.Read callback_at null as no callback due. Read a call again for the corrected values: calls already told keep their version.
Call menu calls end when the call endsA call menu call's ended_at was about 3 seconds after the call ended, while the menu closed the record, and talk_sec and duration_sec counted those seconds.ended_at is when the call ended: the caller hung up, or the conversation ended, whoever hung up first. talk_sec, and duration_sec (every account), no longer count the extra seconds. Call menu calls recorded before this date (and, rarely, a later one) keep the later end.Remove any correction that took 3 seconds off a call menu call.
A call menu call's duration_sec stays the same once it has ended (every key)A read in the first seconds after a call menu call ended could show only the talk time in duration_sec, and the final value could be a second off the record.On a call menu call, duration_sec is the whole record from started_at to ended_at (with the Telephony API, talk_sec plus wait_sec) and stays the same on every read and event once the call reads ended, except a call handed on to a colleague, and rarely a call whose end is corrected.Nothing.
Who hung up a call that came in through a call menu or straight to a team memberSuch calls often read ended_by null. A call menu call the caller hung up could still read null in the first 3 seconds or so after it ended.It reads customer when the caller hung up, and member when your team member's app or browser left the call while the caller was still on. A call menu call the caller hung up usually reads customer from its first read as ended. Calls that rang a team member's own phone can still read null.Nothing.
voicemail.left comes after the terminal eventvoicemail.left could arrive before the call's terminal event. A caller who left a message and stayed on the line to hear your closing words read as ended at once, with an end time that was not the real one.voicemail.left is never sent before the terminal event, and can carry its version. Until such a caller hangs up the call reads live and no event is sent: status ringing (every account), ended_at null, handled_by voicemail and the voicemail block filled in. Then the terminal event follows, and voicemail.left about a second later. If the end of such a call never reaches us, we end it an hour after the message, with the time of the message as its ended_at.Act on voicemail.left by its type and id: never discard it with the rule that applies only a higher version.
response.voicemail_left says when a caller left a voicemail (every key)response.voicemail_left was true only for a message left in a broadcast's guided flow: a voicemail on a call menu, a team member's number or after a transfer read false.It reads true for a caller's voicemail on a call menu, a team member's number or after a transfer, on events for all keys and on Telephony API reads, including reads of older calls at their unchanged version. An event carries what we knew when it was sent: on a team member's number or after a transfer the message is usually stored after the call ends, so the terminal event says false, while voicemail.left and a read say true. Calls an AI voice agent handled keep the earlier rule.With the Telephony API, act on voicemail.left or read the call to know a message was left. Older calls read the corrected value without a new version.
Click to call times in milliseconds, ring secondscustomer_answered_at, and member_answered_at on Phone Bridge, were to the second, and so was ended_at, except on a cancel over the internet before the customer was called, a ring on the team member's web panel or app that ran out or that they declined, a call that could not be placed and a transfer you requested. On Phone Bridge customer_ringing_at was when we noticed the team member's answer, up to a second later, and a click to call whose team member did not answer carried a customer_ringing_at a few seconds after its end. Both ring lengths read 0 on most answered calls and on every Phone Bridge call.Both answer times carry milliseconds. On Phone Bridge customer_ringing_at is the moment the team member's mobile answered, and dial_started_at is null, as it always was. member_ring_sec and customer_ring_sec are whole seconds, rounded down from those times. ended_at usually carries milliseconds too: the moment our server recorded the end. customer_ringing_at is null when the customer was never called. The call record's answered_at and ended_at stay to the second, so they can read up to a second earlier than the click to call's, and a click to call that ends in the same second as an answer never reads an end earlier than that answer.Compare a click to call's times with its call record's to the second, not to the millisecond.
Recording part starts and key press answersOn a Call via SIM call a recording part's started_at was the customer's answer, or null on a call nobody answered; on a transferred click to call it was the colleague's pickup. A broadcast call connected to a team member by a key press took the member's pickup, or nothing, as its answered_at.A Call via SIM part starts when the call began, and a click to call part when the customer answered. The broadcast call keeps the customer's answered_at. Calls from this date; earlier records are not changed.Nothing.
Recording part starts in millisecondsA recording part's started_at read a whole second, up to about a second before the file's first sound.It carries milliseconds: the moment the call's record shows for the start of that file, usually within a second of its first sound. Files stored before this date keep the whole second.Nothing.
GET /calls searches list a call that has just changed state (every key)A page of a status, number, lane, end_detail or has_recording search at or past a count kept from up to 30 seconds earlier was answered with no calls, so a call could be missing from a status list for up to 30 seconds after it changed state.Such a search lists a call that has just changed state at once. total and total_pages follow the page they come with: exact on the page that holds the last match, and while another page follows they count at least one call after this page. A page past the last match answers no calls, and a page 10,000 calls or more past the kept count is answered at once with no calls.Nothing. Read total and total_pages from the page you are on: they can change from one page of a search to the next.
Downloads past the end of the file (every key)A Range past the end of a recording or a voicemail answered 416 with no Content-Range.The 416 carries Content-Range: bytes */<file size> whenever we know the file's size.Nothing. Use the size to ask for a range inside the file.
A download past the end of the file names the call (every key)The 416 answer of the recording and voicemail downloads carried unique_id null.It names the call in unique_id: the same unique_id that Get call status answers for the id in your path. Every other error of those downloads keeps unique_id null.Nothing.
Webhook delivery history is kept for 30 days (every account)The Webhooks tab kept every delivery, with the status code your endpoint returned, for as long as the endpoint existed.From 14 October 2026, each delivery and the status code your endpoint returned are kept for 30 days, then deleted. Deleting an endpoint deletes its delivery history too. The Webhooks tab says so above each endpoint's deliveries.Nothing breaks. To recover an event older than 30 days, read the call (Get call status, or List calls with updated_since on the Telephony API), and keep your own log keyed on X-Agentive-Delivery-Id.

13 October 2026: the call record

Every call on an account with the Telephony API now reads as one complete record, the same on every read and every event, and several values that were wrong on team calls are corrected for every account. AI voice agent calls are unchanged. The details are in the call object and Telephony Webhooks.

What changedIt used toIt nowWhat to do
Every call has a complete record (Telephony API)A call read or event carried 15 to 19 fields: no team member, no answer or end time, no outcome detail, no recording flag, nothing your team saved.The team member, the lane, answer and end times, talk, wait and hold time, the outcome detail (end_detail), who ended the call, the recording with every part, the outcome and note your team saved, voicemail, the call menu key, who it rang, transfers, the campaign, and a version to order by.Nothing breaks: these are new fields. Store each call by call_id and keep the copy with the highest version.
status and end_reason always pair on team calls (every account)On team calls about one row in three carried a pair the docs rule out: a missed dial as missed with completed, an answered call menu call as completed with failed, a voicemail call with no status (queued on Get call status), a call that could not be placed as missed, an unanswered App Agent call as failed.Every read and event of a call your team handles follows the pairing table. A call that reached voicemail reads missed / no_answer; one that could not be placed or connected reads failed / failed; an unanswered App Agent call reads missed. Status filters match what the call reads. AI voice agent calls keep the status, end_reason, duration_sec and events they always had.Remove any workaround that corrected the old values. Branch on the pairs in Status and end reasons.
Events tell the truth on every lane (team calls, every account)An inbound call nobody answered, and a Phone Bridge call the customer never answered, could be sent as call.completed. call.answered came at the call menu's answer, or at your team member's own pickup on Phone Bridge, and never on internet or Call via SIM calls. After a transfer, call.completed came at the transfer with your team member's seconds. A call that ended before it was answered came as call.failed.call.answered fires when the conversation starts: your team member picks up an inbound call, the customer answers an outbound one (Phone Bridge included); with the Telephony API it carries answered_at and the team member. One terminal event per call, at the true end after a transfer, and never again for the same call. A call that ended before an answer is call.no_answer with canceled. A team call's duration_sec on its terminal event is the same value every read gives. AI voice agent calls keep the events and timing they always had.Nothing, if you branch on the event type. A missed inbound call now arrives as call.no_answer or call.busy.
Calls our platform ended read as ours (team calls, every account)A dial that rang out to the one-minute ring limit read missed with canceled, as if your team member had cancelled it (internet calls, and Call via SIM at 60 seconds). An internet call our platform cut about two seconds into its ring (before 12 October 2026 09:29 IST) read missed / no_answer, as if the customer had not answered. An internet call from before 30 September 2026 15:47 IST that never connected could read completed. A click to call your system hung up through the API read ended_before_answer on the internet lane.The ring limit reads missed / no_answer (end_detail customer_no_answer, ended_by system) on every key; the cut dial reads failed / failed (end_detail service_error, network_cause null) and its event is call.failed; the old call that never connected reads missed with its real cause; the click to call reads canceled / canceled with ended_by api on both lanes, as GET /click-to-call says.Nothing, if you branch on the pairs. A report of past calls built from List calls shows these values from now on.
New events, only when tickedAn endpoint with no events ticked received every event, including any added later.call.tagged, call.updated, voicemail.left and recording.failed (Telephony API) reach an endpoint only when ticked by name. An endpoint with nothing ticked keeps receiving the original events.call.member_ringing and call.member_missed come later, only when ticked, announced here. Inbound call.ringing also comes later, announced here: it is one of the original events, so it will then reach an endpoint with nothing ticked too.Tick the new events you want on your endpoint.
Recordingsrecording.available came once per stored file, sometimes before the last part; its duration_sec was the call's length; only the latest part could be downloaded, and not by a click to call id.recording.available comes once per call, about a minute after the last part is stored, with the file's own length; until then a read shows recording.status processing, and revision counts later changes on every account (a recording that reads available is at least revision 1). Every part downloads with ?segment=N, the click to call id works on GET /calls/{id}/recording, and every recording shows expires_at (after it the recording is no longer available).Copy recordings before expires_at. Later file changes arrive as call.updated.
Dashboard campaign calls have their own idEvery call of a dashboard campaign carried the same unique_id, run_<campaign_id>, and GET /calls/run_<campaign_id>/recording streamed the latest attempt's audio.Each one carries its own call_id as unique_id. run_ ids now mean API runs only; a dashboard campaign's run_ id answers 404.Match those calls on call_id.
Click to call ids on every call surfaceA click to call's call events, recording.available and reads carried reference_id and metadata as null and via_api as false.They carry your reference_id, your metadata and via_api true.Nothing.
The click to call object: ring times, talk time, recording (Telephony API)The click to call object carried the start, answer and end times only, and GET /click-to-call paged by page number.The object also carries updated_at, dial_started_at, customer_ringing_at, member_ring_sec, customer_ring_sec, call_duration_sec and the call's recording block, the same on GET /click-to-call, every control answer and every click_to_call.* event. GET /click-to-call also pages with a cursor.Nothing breaks: these are new fields.
charge_inr and transcript_available on team callscharge_inr was null on team calls; transcript_available could be true for a transcript the key could not fetch.charge_inr is what a team call was billed (a broadcast call, or minutes past your plan's included daily calling allowance), else 0. transcript_available is true only when your key can fetch it.Nothing.
Call history sync (Telephony API)List calls paged by page number only, and ignored a query parameter it did not know.updated_since walks every changed call up to a watermark; order=asc and cursor page without gaps; filters by member, reference, click to call, lane, recording and outcome detail. An unknown parameter is reported in warnings, and will later be refused. For every key: a search the index cannot answer on its own (status, number, and the lane, end_detail and has_recording filters) runs two at a time per account, a third at once answers 503 retryable with Retry-After 5, and such a search's total is counted once and kept 30 seconds.See Syncing your call history. Check your requests for parameter names that were silently ignored. Page through a status or number search one request at a time.
New readsNo voicemail route; transcripts for AI calls only; GET /account answered 403 without the wallet feature.GET /calls/{id}/voicemail (Telephony API); team call transcripts on GET /calls/{id}/transcript for accounts with call transcription; GET /account answers every API key, with balance_inr null without the wallet.Nothing.
Clarifiedduration_sec was described as the talk time on every call; team calls were described as not billed per minute.duration_sec keeps the value it always had, so it depends on the lane: the talk time on a connected call your team placed or that rang a team member directly, the whole record on a call menu call, and on a call that did not connect usually the ringing time (0 on Call via SIM and Phone Bridge). talk_sec is the conversation and wait_sec the time before it, one rule on every lane; the two add up to the record from started_at to ended_at. created_at is kept as it was (its text differs between reads and events); use started_at. Team calls are billed per minute only past an included daily allowance or on broadcast campaigns. Digits sent with the keypad (dtmf) endpoint are never stored in call records, events or API logs; call menu key presses are (menu.key, response.digit).Use talk_sec and wait_sec instead of duration_sec.
Smaller correctionsA dialling call read no status; an outbound call the network could not route read missed and sent call.no_answer; GET /calls/{call_id} of a click to call's call answered its call_id as unique_id; from and to took any date text; a number or status search fell back to the backup store during an outage; an AI call placed with POST /ai/calls carried no reference_id in List calls; a team member's own mobile could appear beside their name, or as a number the call rang or was moved to.A dialling call reads ringing. A call the network could not route (RECOVERY_ON_TIMER_EXPIRE, NORMAL_UNSPECIFIED) reads failed and sends call.failed. The click to call id is the unique_id. from and to must be ISO 8601 (else 400). A number or status search during an outage answers 503 retryable. The AI call carries its reference_id. A team member's own mobile is never published beside their name (customer_member, the App Agent lane) or as a number the call rang or was moved to (ring_attempts, transfers). The watermark is ISO 8601 UTC.Retry 503 answers after Retry-After.
Docs correctionsThe call and recording tables left out leg_id, click_to_call_id, metadata, via_api and charge_inr; a recording download was described as a redirect; a rotated secret was said to stop at once; created_to read as exclusive; a 401 was said to be kept for an idempotency key; call.ringing was said to be sent for inbound calls; the retry tail was said to be 24 hours.Every field sent is listed. Downloads stream (200, 206, 416), never a redirect: do not follow redirects. Rotating can keep the old secret for 24 hours. created_to is inclusive. A 401 is never stored for a key. call.ringing is not sent yet. Retries run for about 20 hours.Remove -L and CURLOPT_FOLLOWLOCATION from recording downloads.

October 2026

What changedIt used toIt nowWhat to do
Click to Call APIA call between your team member and a customer could only be started by the team member, from the Agent Panel or the app.A full Click to Call API reference: list team members, start a call that rings your team member first, control it, and receive the signed click_to_call.* events. It needs the Telephony API on the account.Nothing breaks. A call started this way also appears in the call events and reads, where unique_id is the click to call id (c2c_...) and the call object carries click_to_call_id.
Every call for accounts with the Telephony APIAn account with the AI voice agent and not voice broadcast read and received webhooks for its AI calls only.An account with the Telephony API reads and receives webhooks for all its calls, its team's calls included, whatever other products it has.If your account has the AI voice agent and you want AI calls only, filter on agent_id or campaign_type in your handler.
Also new in October
GET /account reports products.click_to_call. Rotating your secret in API Access can now keep the old secret working for 24 hours, so a planned change needs no downtime; stopping the old secret at once is still the default. API Access shows when your keys were last used.

September 2026

What changedIt used toIt nowWhat to do
Webhook verification is version 2 only (29 Sep)The samples verified X-Agentive-Signature-V2 when present and fell back to the body-only X-Agentive-Signature when it was absent.Every sample verifies X-Agentive-Signature-V2 only, rejects a timestamp older than five minutes, and refuses a delivery that does not carry it. Every delivery carries it.Remove any fallback to X-Agentive-Signature from your receiver. A body-only signature can be replayed by anyone who captured one delivery, so accepting it keeps that door open.
Recordings are streamed (29 Sep)GET /calls/:unique_id/recording usually answered 302 with a short-lived download link, and the samples told your client to follow it.The API answers 200 with the audio itself (206 for a Range request) and never redirects. The samples authenticate with HTTP Basic.Nothing breaks: a client that followed the redirect reads the audio directly now. Stop sending your secret to any host other than the API; custom headers such as x-api-secret are carried across a redirect by most HTTP clients.
AI voice agent API documented (29 Sep)POST /ai/calls worked but was undocumented, and an AI voice agent API campaign could not be triggered.A full AI Voice Agent API reference. The trigger runs AI campaigns and takes variables and metadata, and AI calls fire call.analysed.Invalid variables are now refused with 400 validation_error naming the key, instead of being dropped. Check the rules before you send them.
A wrong secret is a 401A known publishable key sent with a wrong secret returned 403.Returns 401, with the same "Invalid API credentials." sentence, so the status can no longer tell an attacker that a key exists.Move any branch that read 403 as a bad secret to 401. On the Voice APIs, 401 now always means the credentials were rejected and 403 always means they were accepted without entitlement. Since 17 October 2026 two answers are not about your key: https_required (403) refuses a plain HTTP request to api.agentive.co.in before your key is read, and a recording link, which carries no key, can answer invalid_link (401), link_expired or link_revoked (403).
Webhook status matches the eventdata.status could disagree with the event name: a call that rang unanswered or was busy sometimes arrived as failed, and a call that could not be placed sometimes arrived as missed.data.status is derived from the event name, so call.no_answer and call.busy are always missed and call.failed is always failed.Nothing, if you branch on the event type or on end_reason. Remove any workaround that corrected the old values.
Webhook User-AgentAn internal build string that did not match the Agentive-Webhooks/... form the docs promised.Agentive-Webhooks/2026-06-01, the payload version, so it changes only when api_version does.Update any allow-list or log filter that matched the old string. Never authenticate a delivery on the User-Agent; verify the signature.
unique_id on a direct AI callEvents after call.initiated for a call placed straight to an AI agent carried an internal session id in data.unique_id, not the id the placing response returned.data.unique_id is the id you were given when you placed the call, on every event, and unique_id is the same on every read of the call.Nothing for broadcast, Interactive Voice or verification calls; their ids are unchanged. For direct AI calls, match on the id the placing response returned, which now works throughout.
Also on 29 September
A request's Idempotency-Key longer than 128 characters is refused with HTTP 400 instead of being cut short. The per-address limit before authentication now counts only requests refused with 401 or 403, and failed secrets are counted per publishable key and client address, so a correct secret is always let through. Every webhook address must use https:// on port 443 or 8443, checked on every delivery, so an address saved earlier on plain http:// or another port needs changing. A custom signing secret must be at least 32 characters, and an account can register up to 10 endpoints. An account with the AI voice agent and not voice broadcast reads and receives webhooks for its AI calls only; any other account, including one with neither product, reads and receives all its calls. The number_flood and daily_cap refusals carry Retry-After and retry_after_sec.
Also new, and safe to ignore until you want it
A string error_code beside the numeric code on every Voice error, an error key carrying the same sentence as details, Retry-After on every 429 and 409, X-RateLimit-* aliases, X-Agentive-Delivery-Id and X-Agentive-Attempt on webhook deliveries, a webhook retry tail that keeps trying for about 20 hours, created_at_ist and created_at_utc on the call object, and verification_status on verifications.

Need help?

Stuck on an integration, or need something the API does not cover yet? Write to the team and an engineer will reply.

Contact us