MCP server

Call ID

Call ID (from revox_make_call response)

Seconds between each status fetch (default 5)

E.164 phone number (e.g. +1234567890)

Values of the assistant's {{variables}} for this call, keyed by variable name, whether the call uses assistant_id or an inline assistant. Send every variable the prompt and first sentence use. A missing or empty one is not rejected: the prompt reads '(name: not provided)' in its place, and a static first sentence leaves it out.

Your own key/value pairs to store with the call, e.g. your CRM ID. They come back as sent on the call.

Caller ID of the call, in E.164 format: one of your organization's numbers (GET /phone-numbers). Omitted: the assistant's from_phone_number, or else a Revox number chosen for the destination.

Start the call at this date and time (ISO 8601, e.g. 2026-11-03T10:00:00+01:00) instead of now.

Limit the number of concurrent calls for a given concurrency key. The limit itself is set server-side; omit this to leave the call ungrouped (bounded only by your organization's limit).

Dial even outside the assistant's calling window (default true): the first dial ignores calling windows, allowed days and excluded dates. Set false to respect them (required for call_retry_config.excluded_dates to hold the first dial): the call then waits for the next open window.

IANA timezone of this call, in place of its campaign's or assistant's timezone. Examples: 'America/Los_Angeles', 'Europe/Paris'. The call runs in exactly this one timezone: its calling windows and allowed days are read in it, the agent tells the date and offers calendar slots in it, and callbacks and extracted datetimes are interpreted in it. Omitted or null: the campaign's timezone, else the assistant's. It is never derived from the phone number.

ID of an existing assistant to use. When provided, prompt/voice_provider/voice_id are ignored.

Custom prompt for the call. Required when assistant_id is not provided.

Optional voice provider override (e.g. cartesia). Ignored when assistant_id is provided. If omitted, auto-selected from phone number country.

Optional voice ID override. Ignored when assistant_id is provided. If omitted, auto-selected from phone number country.

Voice volume for Cartesia only (0.5–2.0, default 1.0). Ignored when assistant_id or non-Cartesia provider.

The agent's opening line, spoken word for word. Only used, and only kept, with first_sentence_mode 'static': with 'generated' or 'none' it is dropped and reads back empty. May contain {{variable}} placeholders; one without a value is left out.

How the agent opens the call. Default at creation: 'generated'.

Sentence the agent says, without being interruptible, when it decides to end the call. Null or empty: the agent says a short default goodbye, only if it has not said goodbye already.

If set, when voicemail is detected the agent will speak this message then hang up; if null, hang up immediately. Left on the first attempt only (second dial of a double call). Takes the same {{variables}} as the prompt (e.g. "Hi {{first_name}}, this is Julie from Acme, please call us back.").

Longest a call may last, in seconds: the agent then says max_duration_end_message, if set, and hangs up. Default at creation: 300. Outbound calls are capped at 600.

The values to extract from each call (e.g. an email, a budget, a date). They land in structured_output of each call attempt, keyed by name.

Custom prompt for structured data extraction. If not provided, a default prompt is used. Available variables: {{transcript}}, {{call_direction}}, {{user_phone_number}}, {{agent_phone_number}}.

URL that receives a POST with the call and this assistant once the call is over, when it reaches completed or errored (not when it is cancelled). See Webhooks for the payload.

Custom API tools the assistant can call during conversations. Each tool defines an HTTP endpoint with variable substitution. Null or empty when the assistant has none.

Post-call instructions: what a separate AI agent does once the call has ended (answered or not: voicemails and unanswered calls get it too). It reads the call (transcript, outcome, summary, structured_output, prompt variables, what was done during the call) and acts with the tools below. Empty or null: nothing runs after the call. How to write them: - Plain language, in the language you want, one step per line, each as a condition then an action: "If the prospect asked to be called back, ...". A call that meets no condition gets nothing, which is the expected result. - Name each action by its tool, as @tool_name: the agent can only act through these tools, never by itself. - To send an exact text, put it in quotes: it is sent word for word. Otherwise the agent writes the message itself, in the language of the call, from facts of the call only. - {{variables}} are filled in before the agent reads them: the call's prompt variables, each structured_output field by its name, and {{outcome}}, {{outcome_summary}}. - Pick the email tool by who reads it: @send_email writes to the person who was on the call (their address on file or one they gave), with only the text you ask for; @notify_team_by_email writes to your own team, at the address you name, with the call report and a link to the call. Say which address each team email goes to, and which channel each Slack or Teams message goes to. Texts always go to the person on the call. - Actions already taken during the call (an SMS sent by @send_sms from the call prompt, a booking, a transfer) are never repeated. Tools: - @send_email (always available; at most 3 per call): Emails the person who was on the call (the prospect, the customer), like @send_sms texts them. The address is the contact's email on file, or one the person gave during the call; it never goes anywhere else. The email carries only the subject and the text the instructions ask for: no call report, no link to the dashboard. The instructions can name the sender and a reply-to address. Can carry a calendar invite for the callback time the call produced. To tell your own team about the call, use @notify_team_by_email. Example: If the prospect asked for the brochure, send them an email with @send_email, subject "Votre brochure", with the link https://example.com/brochure. - @notify_team_by_email (always available; at most 5 per call): Emails your own team about the call, at any address the instructions name, which can depend on the call (billing@ for a billing question, shipping@ for a delivery). By default the subject is "{outcome}: {contact}" and the email includes the contact, the call outcome, the extracted data, the summary and a "View the call" link to the dashboard. The instructions can give another subject and leave sections or the link out. Can carry a calendar invite for the callback time the call produced. Never for the person who was on the call: that is @send_email. Example: If a meeting was booked, notify sales@company.com with @notify_team_by_email with the prospect's name, number and the agreed date. - @send_sms (always available; at most 3 per call): Texts the person on the call (the callee outbound, the caller inbound), under 300 characters, in the language of the call. Not available on web test calls (no phone number). Also usable during the call, from the call prompt. Example: If nobody answered, send an SMS with @send_sms: "Bonjour, ici Julie de Revox, je vous rappelle demain matin." - @post_slack_message (requires a Slack workspace connected, with channels chosen, in the assistant's Team alerts tab of the dashboard; without it the tool is not offered; at most 5 per call): Posts in one of the Slack channels connected to the assistant (named in the instructions, e.g. #sales). Revox adds the assistant's name and a link to the call. Example: Post the call outcome and summary in #sales with @post_slack_message. - @post_teams_message (requires a Microsoft Teams workspace connected, with channels chosen, in the assistant's Team alerts tab of the dashboard; without it the tool is not offered; at most 5 per call): Posts in one of the Microsoft Teams channels connected to the assistant, named "Team / Channel". Revox adds the assistant's name and a link to the call. Example: When the prospect is interested, post a short summary in Sales / Leads with @post_teams_message. - @crm_push_call (requires Zoho CRM connected, or HubSpot connected with post-call sync on, in the assistant's Integrations tab of the dashboard; without it the tool is not offered; at most 1 per call): Records the call in the connected CRM (Zoho, or HubSpot with post-call sync on): the contact is created or updated from their number and the call attached with its outcome, summary, extracted data and recording. The instructions can add a note. With HubSpot sync on, it also runs by itself after every call someone answered, unless the instructions mention the CRM (then they decide). Example: After every answered call, @crm_push_call with a two-sentence note: the prospect's need, then the next step.

Where calls can be transferred to when users ask to speak to a human. With a single entry the assistant always transfers there; with several, it picks one at transfer time by applying the routing rules written in the assistant's own prompt (which refer to the destination labels). Empty or null disables transfer.

How calls are transferred to transfer_destinations. Default: 'warm'. Ignored without transfer destinations.

When using warm transfer: extra instructions for the supervisor handoff summary. If null or empty, the API uses the product default briefing when the call is loaded for the agent.

When using warm transfer: voice speed used only while the AI briefs the human colleague. Same range as voice.speed. Omit or null to brief at the assistant's voice speed.

Free-text search. A call matches when it contains every word of the query (3 characters or more, in any order) in its phone numbers, contact identity, metadata or prompt variable values, or in the extracted data of its last attempt. A phone number typed with spaces or a leading 0 is matched on its digits.

Keep calls in any of these statuses. A scheduled call of a paused campaign counts as 'paused'.

Keep calls in any of these directions.

Keep calls whose last attempt has one of these results (who answered: human, voicemail, IVR...). 'none' matches calls whose last attempt has no result yet, or no attempt at all.

Keep calls with one of these business outcomes. 'none' matches calls without an outcome, 'do_not_call' calls whose number is on the do-not-call list (those match no other outcome value).

Keep calls placed with one of these assistants. A step of a multi-step flow matches the calls that went through it. 'none' matches calls whose assistant was deleted.

Keep calls of one of these campaigns. With this filter, a call superseded by the prospect calling back is left out, so each contact is listed once.

Keep calls whose from_phone_number is one of these numbers (your number for an outbound call, the caller's for an inbound one), in E.164 format, exact match.

Keep calls assigned to one of these team members (user IDs, see the call's assignee.id). 'none' matches unassigned calls.

Keep calls whose metadata (or, when the metadata has no such key, prompt variables) hold all these values.

Keep calls whose to_phone_number is this number (the person called for an outbound call, your number for an inbound one), in E.164 format, exact match. Ignored by POST /call/export.

Keep only the calls with these IDs. Ignored by POST /call/export.

Page number, starting at 1. Default: 1.

Number of calls per page, 1 to 100. Default: 50.

Sort order. 'updated_at' (the default): most recent activity. 'duration': talk time of the last attempt, calls without one last. 'priority': a fixed order for working a campaign (live calls, then calls a person from your team joined, hot leads, calls a person answered, queued, scheduled, the rest), which ignores sort_direction. 'structured_output.<field>': a value extracted from the last attempt.

'asc' or 'desc' (the default).

The guide's « parcours et exemples » that match the case (cold call, lead follow-up, inbound reception, switchboard, objections...). Omit when none applies.

System prompt given to the LLM for the whole call: who the agent is, its goal and how to run the conversation. May contain {{variable}} placeholders, filled from the call's prompt_variables.

Required. The guide_version returned by revox_get_prompt_guide. Call that tool and write the prompt following its guide before calling this one.

IANA timezone of this assistant's calls, e.g. 'Europe/Paris' or 'America/Phoenix'. Every call runs in exactly one timezone: its calling windows and allowed days are read in it, the agent tells the date and offers calendar slots in it, and callbacks and extracted datetimes are interpreted in it. A campaign's timezone, then POST /call timezone, override it for their calls. Default when creating: 'Europe/Paris'. Replaces the deprecated call_retry_config.timezone.

The agent's opening line, spoken word for word. Only used, and only kept, with first_sentence_mode 'static': with 'generated' or 'none' it is dropped and reads back empty. May contain {{variable}} placeholders; one without a value is left out.

How the agent opens the call. Default at creation: 'generated'.

Sentence the agent says, without being interruptible, when it decides to end the call. Null or empty: the agent says a short default goodbye, only if it has not said goodbye already.

If set, when voicemail is detected the agent will speak this message then hang up; if null, hang up immediately. Left on the first attempt only (second dial of a double call). Takes the same {{variables}} as the prompt (e.g. "Hi {{first_name}}, this is Julie from Acme, please call us back.").

Longest a call may last, in seconds: the agent then says max_duration_end_message, if set, and hangs up. Default at creation: 300. Outbound calls are capped at 600.

The values to extract from each call (e.g. an email, a budget, a date). They land in structured_output of each call attempt, keyed by name.

Custom prompt for structured data extraction. If not provided, a default prompt is used. Available variables: {{transcript}}, {{call_direction}}, {{user_phone_number}}, {{agent_phone_number}}.

URL that receives a POST with the call and this assistant once the call is over, when it reaches completed or errored (not when it is cancelled). See Webhooks for the payload.

Custom API tools the assistant can call during conversations. Each tool defines an HTTP endpoint with variable substitution. Null or empty when the assistant has none.

Post-call instructions: what a separate AI agent does once the call has ended (answered or not: voicemails and unanswered calls get it too). It reads the call (transcript, outcome, summary, structured_output, prompt variables, what was done during the call) and acts with the tools below. Empty or null: nothing runs after the call. How to write them: - Plain language, in the language you want, one step per line, each as a condition then an action: "If the prospect asked to be called back, ...". A call that meets no condition gets nothing, which is the expected result. - Name each action by its tool, as @tool_name: the agent can only act through these tools, never by itself. - To send an exact text, put it in quotes: it is sent word for word. Otherwise the agent writes the message itself, in the language of the call, from facts of the call only. - {{variables}} are filled in before the agent reads them: the call's prompt variables, each structured_output field by its name, and {{outcome}}, {{outcome_summary}}. - Pick the email tool by who reads it: @send_email writes to the person who was on the call (their address on file or one they gave), with only the text you ask for; @notify_team_by_email writes to your own team, at the address you name, with the call report and a link to the call. Say which address each team email goes to, and which channel each Slack or Teams message goes to. Texts always go to the person on the call. - Actions already taken during the call (an SMS sent by @send_sms from the call prompt, a booking, a transfer) are never repeated. Tools: - @send_email (always available; at most 3 per call): Emails the person who was on the call (the prospect, the customer), like @send_sms texts them. The address is the contact's email on file, or one the person gave during the call; it never goes anywhere else. The email carries only the subject and the text the instructions ask for: no call report, no link to the dashboard. The instructions can name the sender and a reply-to address. Can carry a calendar invite for the callback time the call produced. To tell your own team about the call, use @notify_team_by_email. Example: If the prospect asked for the brochure, send them an email with @send_email, subject "Votre brochure", with the link https://example.com/brochure. - @notify_team_by_email (always available; at most 5 per call): Emails your own team about the call, at any address the instructions name, which can depend on the call (billing@ for a billing question, shipping@ for a delivery). By default the subject is "{outcome}: {contact}" and the email includes the contact, the call outcome, the extracted data, the summary and a "View the call" link to the dashboard. The instructions can give another subject and leave sections or the link out. Can carry a calendar invite for the callback time the call produced. Never for the person who was on the call: that is @send_email. Example: If a meeting was booked, notify sales@company.com with @notify_team_by_email with the prospect's name, number and the agreed date. - @send_sms (always available; at most 3 per call): Texts the person on the call (the callee outbound, the caller inbound), under 300 characters, in the language of the call. Not available on web test calls (no phone number). Also usable during the call, from the call prompt. Example: If nobody answered, send an SMS with @send_sms: "Bonjour, ici Julie de Revox, je vous rappelle demain matin." - @post_slack_message (requires a Slack workspace connected, with channels chosen, in the assistant's Team alerts tab of the dashboard; without it the tool is not offered; at most 5 per call): Posts in one of the Slack channels connected to the assistant (named in the instructions, e.g. #sales). Revox adds the assistant's name and a link to the call. Example: Post the call outcome and summary in #sales with @post_slack_message. - @post_teams_message (requires a Microsoft Teams workspace connected, with channels chosen, in the assistant's Team alerts tab of the dashboard; without it the tool is not offered; at most 5 per call): Posts in one of the Microsoft Teams channels connected to the assistant, named "Team / Channel". Revox adds the assistant's name and a link to the call. Example: When the prospect is interested, post a short summary in Sales / Leads with @post_teams_message. - @crm_push_call (requires Zoho CRM connected, or HubSpot connected with post-call sync on, in the assistant's Integrations tab of the dashboard; without it the tool is not offered; at most 1 per call): Records the call in the connected CRM (Zoho, or HubSpot with post-call sync on): the contact is created or updated from their number and the call attached with its outcome, summary, extracted data and recording. The instructions can add a note. With HubSpot sync on, it also runs by itself after every call someone answered, unless the instructions mention the CRM (then they decide). Example: After every answered call, @crm_push_call with a two-sentence note: the prospect's need, then the next step.

Where calls can be transferred to when users ask to speak to a human. With a single entry the assistant always transfers there; with several, it picks one at transfer time by applying the routing rules written in the assistant's own prompt (which refer to the destination labels). Empty or null disables transfer.

How calls are transferred to transfer_destinations. Default: 'warm'. Ignored without transfer destinations.

When using warm transfer: extra instructions for the supervisor handoff summary. If null or empty, the API uses the product default briefing when the call is loaded for the agent.

When using warm transfer: voice speed used only while the AI briefs the human colleague. Same range as voice.speed. Omit or null to brief at the assistant's voice speed.

Inbound calls only. URL fetched over HTTP GET right before the call is answered, with {{phone}} replaced by the caller's number in E.164 format (URL-encoded), to fill the {{variable}} placeholders the assistant declares. It answers either {"prompt_variables": {...}} or a flat JSON object whose top-level fields are the variables. The call is always answered: if the endpoint fails, takes more than 3 seconds, answers 404 or leaves a variable out, the missing variables are marked as not provided. Must be an http(s) URL containing {{phone}}. When null, no lookup is performed.

HTTP headers sent with the pre-call lookup request, e.g. an API key. Null or empty when the endpoint needs none.

Voice provider. Use with voice_id. To let the user choose by ear, use revox_pick_voice; otherwise revox_list_voices (pick a voice whose language matches the prompt).

Voice ID. Use with voice_provider. For French, use revox_list_voices and pick a voice with language 'fr', or Cartesia id a249eaff-1e96-4d2c-b23b-12efa4f66f41.

Voice speed (default 1.0).

Voice volume for Cartesia only (0.5–2.0, default 1.0). Ignored for other providers.

Cartesia TTS model (Cartesia only, default sonic-3.6). Ignored for other providers.

The guide_version returned by revox_get_prompt_guide. Required when prompt or first_sentence is passed.

System prompt given to the LLM for the whole call: who the agent is, its goal and how to run the conversation. May contain {{variable}} placeholders, filled from the call's prompt_variables.

IANA timezone of this assistant's calls, e.g. 'Europe/Paris' or 'America/Phoenix'. Every call runs in exactly one timezone: its calling windows and allowed days are read in it, the agent tells the date and offers calendar slots in it, and callbacks and extracted datetimes are interpreted in it. A campaign's timezone, then POST /call timezone, override it for their calls. Default when creating: 'Europe/Paris'. Replaces the deprecated call_retry_config.timezone.

The agent's opening line, spoken word for word. Only used, and only kept, with first_sentence_mode 'static': with 'generated' or 'none' it is dropped and reads back empty. May contain {{variable}} placeholders; one without a value is left out.

How the agent opens the call. Default at creation: 'generated'.

Sentence the agent says, without being interruptible, when it decides to end the call. Null or empty: the agent says a short default goodbye, only if it has not said goodbye already.

If set, when voicemail is detected the agent will speak this message then hang up; if null, hang up immediately. Left on the first attempt only (second dial of a double call). Takes the same {{variables}} as the prompt (e.g. "Hi {{first_name}}, this is Julie from Acme, please call us back.").

Longest a call may last, in seconds: the agent then says max_duration_end_message, if set, and hangs up. Default at creation: 300. Outbound calls are capped at 600.

The values to extract from each call (e.g. an email, a budget, a date). They land in structured_output of each call attempt, keyed by name.

Custom prompt for structured data extraction. If not provided, a default prompt is used. Available variables: {{transcript}}, {{call_direction}}, {{user_phone_number}}, {{agent_phone_number}}.

URL that receives a POST with the call and this assistant once the call is over, when it reaches completed or errored (not when it is cancelled). See Webhooks for the payload.

Custom API tools the assistant can call during conversations. Each tool defines an HTTP endpoint with variable substitution. Null or empty when the assistant has none.

Post-call instructions: what a separate AI agent does once the call has ended (answered or not: voicemails and unanswered calls get it too). It reads the call (transcript, outcome, summary, structured_output, prompt variables, what was done during the call) and acts with the tools below. Empty or null: nothing runs after the call. How to write them: - Plain language, in the language you want, one step per line, each as a condition then an action: "If the prospect asked to be called back, ...". A call that meets no condition gets nothing, which is the expected result. - Name each action by its tool, as @tool_name: the agent can only act through these tools, never by itself. - To send an exact text, put it in quotes: it is sent word for word. Otherwise the agent writes the message itself, in the language of the call, from facts of the call only. - {{variables}} are filled in before the agent reads them: the call's prompt variables, each structured_output field by its name, and {{outcome}}, {{outcome_summary}}. - Pick the email tool by who reads it: @send_email writes to the person who was on the call (their address on file or one they gave), with only the text you ask for; @notify_team_by_email writes to your own team, at the address you name, with the call report and a link to the call. Say which address each team email goes to, and which channel each Slack or Teams message goes to. Texts always go to the person on the call. - Actions already taken during the call (an SMS sent by @send_sms from the call prompt, a booking, a transfer) are never repeated. Tools: - @send_email (always available; at most 3 per call): Emails the person who was on the call (the prospect, the customer), like @send_sms texts them. The address is the contact's email on file, or one the person gave during the call; it never goes anywhere else. The email carries only the subject and the text the instructions ask for: no call report, no link to the dashboard. The instructions can name the sender and a reply-to address. Can carry a calendar invite for the callback time the call produced. To tell your own team about the call, use @notify_team_by_email. Example: If the prospect asked for the brochure, send them an email with @send_email, subject "Votre brochure", with the link https://example.com/brochure. - @notify_team_by_email (always available; at most 5 per call): Emails your own team about the call, at any address the instructions name, which can depend on the call (billing@ for a billing question, shipping@ for a delivery). By default the subject is "{outcome}: {contact}" and the email includes the contact, the call outcome, the extracted data, the summary and a "View the call" link to the dashboard. The instructions can give another subject and leave sections or the link out. Can carry a calendar invite for the callback time the call produced. Never for the person who was on the call: that is @send_email. Example: If a meeting was booked, notify sales@company.com with @notify_team_by_email with the prospect's name, number and the agreed date. - @send_sms (always available; at most 3 per call): Texts the person on the call (the callee outbound, the caller inbound), under 300 characters, in the language of the call. Not available on web test calls (no phone number). Also usable during the call, from the call prompt. Example: If nobody answered, send an SMS with @send_sms: "Bonjour, ici Julie de Revox, je vous rappelle demain matin." - @post_slack_message (requires a Slack workspace connected, with channels chosen, in the assistant's Team alerts tab of the dashboard; without it the tool is not offered; at most 5 per call): Posts in one of the Slack channels connected to the assistant (named in the instructions, e.g. #sales). Revox adds the assistant's name and a link to the call. Example: Post the call outcome and summary in #sales with @post_slack_message. - @post_teams_message (requires a Microsoft Teams workspace connected, with channels chosen, in the assistant's Team alerts tab of the dashboard; without it the tool is not offered; at most 5 per call): Posts in one of the Microsoft Teams channels connected to the assistant, named "Team / Channel". Revox adds the assistant's name and a link to the call. Example: When the prospect is interested, post a short summary in Sales / Leads with @post_teams_message. - @crm_push_call (requires Zoho CRM connected, or HubSpot connected with post-call sync on, in the assistant's Integrations tab of the dashboard; without it the tool is not offered; at most 1 per call): Records the call in the connected CRM (Zoho, or HubSpot with post-call sync on): the contact is created or updated from their number and the call attached with its outcome, summary, extracted data and recording. The instructions can add a note. With HubSpot sync on, it also runs by itself after every call someone answered, unless the instructions mention the CRM (then they decide). Example: After every answered call, @crm_push_call with a two-sentence note: the prospect's need, then the next step.

Where calls can be transferred to when users ask to speak to a human. With a single entry the assistant always transfers there; with several, it picks one at transfer time by applying the routing rules written in the assistant's own prompt (which refer to the destination labels). Empty or null disables transfer.

How calls are transferred to transfer_destinations. Default: 'warm'. Ignored without transfer destinations.

When using warm transfer: extra instructions for the supervisor handoff summary. If null or empty, the API uses the product default briefing when the call is loaded for the agent.

When using warm transfer: voice speed used only while the AI briefs the human colleague. Same range as voice.speed. Omit or null to brief at the assistant's voice speed.

Inbound calls only. URL fetched over HTTP GET right before the call is answered, with {{phone}} replaced by the caller's number in E.164 format (URL-encoded), to fill the {{variable}} placeholders the assistant declares. It answers either {"prompt_variables": {...}} or a flat JSON object whose top-level fields are the variables. The call is always answered: if the endpoint fails, takes more than 3 seconds, answers 404 or leaves a variable out, the missing variables are marked as not provided. Must be an http(s) URL containing {{phone}}. When null, no lookup is performed.

HTTP headers sent with the pre-call lookup request, e.g. an API key. Null or empty when the endpoint needs none.

Voice provider. Use with voice_id. To let the user choose by ear, use revox_pick_voice; otherwise revox_list_voices (pick a voice whose language matches the prompt).

Voice ID. Use with voice_provider. For French, use revox_list_voices and pick a voice with language 'fr', or Cartesia id a249eaff-1e96-4d2c-b23b-12efa4f66f41.

Voice speed (default 1.0).

Voice volume for Cartesia only (0.5–2.0, default 1.0). Ignored for other providers.

Cartesia TTS model (Cartesia only, default sonic-3.6). Ignored for other providers.

Language of the issue messages. Defaults to en.

The provider of the voice.

Only offer voices in this language: the language the assistant speaks (e.g. 'fr'). Omit to offer every language.

What the voice is for, shown on the page (e.g. "l'accueil téléphonique du cabinet Martin").

pick_id from revox_pick_voice

Adds a calendar on this provider. Omit with calendar_id.

An existing calendar with no account, from revox_list_calendars. Omit with provider.

Label shown in the dashboard, naming where the key will be used (e.g. 'Codex - CRM sync').

ID of the live call.

How long the link can be opened, in seconds, from 30 to 3600. Default 300 (5 minutes). Keep it short: anyone holding the link can listen to the call and talk to the person on the line. Expiry only stops new openings: a page already connected to the call stays connected until the call ends.

true: turn the page on with a new link (regenerates it if already on). false: turn it off.

Start of the period, ISO 8601 (e.g. 2026-11-01T00:00:00+01:00). Default: the start of the current month in timezone.

End of the period, excluded, ISO 8601. Default: now.

Size of each point of series. Default: hour up to 2 days, day up to 92 days, week up to a year, month beyond. At most 400 points.

IANA timezone the points and the default period are cut in. Default: Europe/Paris.