{"id":"de.echocall/echocall","slug":"de-echocall-echocall","title":"EchoCall","description":"Run EchoCall AI phone and chat agents from ChatGPT or Claude: calls, agents, knowledge and numbers.","version":"1.23.0","publisher":{"kind":"domain","id":"echocall.de","label":"echocall.de","url":"https://echocall.de"},"website":"https://echocall.de/en/mcp","repository":"https://github.com/ECHOCALL-LLC/echocall-mcp","remotes":[{"type":"streamable-http","url":"https://hub.echocall.de/mcp"}],"packages":[],"published":"2026-11-18","updated":"2026-11-18","status":"online","auth":"","latency_ms":2169,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"list_agents","title":"List voice agents","description":"List voice agents\n\nReturns the voice agents visible to the key, one page at a time, with a real total from a separate count query. An ordinary account key sees only its own agents; a reseller key sees every agent belonging to that reseller and can narrow the result to one customer with `userId`. Each item is the list form of an agent: no prompt, no model settings and no privacy settings, so fetch ","read_only":true},{"name":"create_agent","title":"Create a voice agent","description":"Create a voice agent\n\nCreates a voice agent and provisions it in the voice engine in the same request, so the agent is ready to take calls as soon as the call succeeds. Only `name` and `language` are required; every other field falls back to a platform default, and `language` is normalised to a two-letter code, so a value like \"german\" is stored as `de`. The response is a short acknowledgement rat","read_only":false},{"name":"get_agent","title":"Get a voice agent","description":"Get a voice agent\n\nReturns the full public configuration of one voice agent, including the system prompt, the opening line, model settings and the recording and retention settings. Internal voice engine identifiers are never included. A reseller key may read any agent belonging to that reseller; an ordinary key only its own. An identifier that is not a number after the `agent_` prefix is removed i","read_only":true},{"name":"update_agent","title":"Update a voice agent","description":"Update a voice agent\n\nChanges one or more fields on a voice agent. Every field is optional and only the fields you send are written, so this is a partial update. The change is pushed to the voice engine first and then stored; if the engine rejects the push the request still succeeds and the new values are stored, so a caller that depends on live behaviour should verify the agent afterwards. The re","read_only":false},{"name":"delete_agent","title":"Delete a voice agent","description":"IRREVERSIBLE: Delete a voice agent\n\nDeletes a voice agent permanently and removes it from the voice engine. This cannot be undone, and any phone number still routed to this agent stops being answered by it. Its integration links and knowledge entries are deleted with it, and so are the indexed knowledge documents that no other agent uses. The removal in the voice engine is attempted first, but a f","read_only":false},{"name":"list_agent_integrations","title":"List integrations assigned to an agent","description":"List integrations assigned to an agent\n\nReturns every integration currently assigned to this voice agent, together with the tools the agent may call through it. The `enabledTools` field decides which of the integration actions the assistant may call: null means the recommended default set for that integration type, an empty array means the assistant may call nothing, and a list of tool names means","read_only":true},{"name":"assign_agent_integration","title":"Assign an integration to an agent","description":"Assign an integration to an agent\n\nGives a voice agent access to one integration, so its tools become callable during a call. The integration must belong to the account that owns the agent, which for a reseller key is the customer account, not the reseller. The `enabledTools` field decides which of the integration actions the assistant may call: null means the recommended default set for that inte","read_only":false},{"name":"update_agent_integration_tools","title":"Change the tool selection for an assigned integration","description":"Change the tool selection for an assigned integration\n\nReplaces the tool selection for one integration already assigned to a voice agent. The `enabledTools` field decides which of the integration actions the assistant may call: null means the recommended default set for that integration type, an empty array means the assistant may call nothing, and a list of tool names means exactly those tools an","read_only":false},{"name":"remove_agent_integration","title":"Remove an integration from an agent","description":"IRREVERSIBLE: Remove an integration from an agent\n\nUnassigns an integration from a voice agent, so the agent can no longer call any of its tools. The integration itself is untouched and stays available to assign elsewhere. The reduced tool set is pushed to the voice engine after the row is removed; if that push fails the request returns 502 and the integration is already unassigned locally but may","read_only":false},{"name":"list_agent_knowledge","title":"List agent knowledge sources","description":"List agent knowledge sources\n\nReturns every knowledge source attached to one voice agent, newest first. These are the documents the agent may draw on when answering, added either as a crawled web page or as literal text. The response is a plain list with no paging. Entries belong to the account that owns the agent, so a reseller key that reads a customer agent sees the same entries as the customer","read_only":true},{"name":"add_agent_knowledge","title":"Add a knowledge source to an agent","description":"Add a knowledge source to an agent\n\nAdds one knowledge source to a voice agent. The body is one of three shapes chosen by `type`: `url` reads one page and reads it again every `syncInterval` (weekly by default), `text` takes up to 200000 characters of `text` to store verbatim, `crawl` reads a whole website from its start page, up to `maxDepth` links deep and `maxPages` pages, and crawls it again e","read_only":false},{"name":"add_agent_knowledge_file","title":"Add a file to an agent knowledge base","description":"Add a file to an agent knowledge base\n\nAdds a file as knowledge source to a voice agent, as the dashboard upload does. Send the file as base64 in `base64` with its name in `fileName`. Allowed are PDF, TXT, MD, CSV and JSON files of at most 15 MB; the content must match the extension (a PDF starts with `%PDF-`, text files are UTF-8), otherwise the request is rejected with 400. Over MCP the whole re","read_only":false},{"name":"delete_agent_knowledge","title":"Delete an agent knowledge source","description":"IRREVERSIBLE: Delete an agent knowledge source\n\nRemoves one knowledge source from a voice agent: the entry is deleted and the agent no longer draws on the document. The indexed document is deleted from the voice engine as well, unless another entry or another agent still uses it. The entry must belong to this agent, otherwise the request is rejected with 404. A failure in the voice engine is logge","read_only":false},{"name":"refresh_agent_knowledge","title":"Refresh an agent knowledge source","description":"Refresh an agent knowledge source\n\nRe-reads a URL knowledge source from its source page immediately and replaces the stored content with what the page says now. Website sources are also re-read on a schedule, so this is for the case where a page changed and the agent should know about it at once. Only entries of type `url` can be refreshed; text and file entries are rejected with 400. The entry mu","read_only":false},{"name":"list_chatbots","title":"List chatbots","description":"List chatbots\n\nReturns the chatbots visible to the key, newest first. An ordinary account key sees only its own chatbots; a reseller key sees every chatbot belonging to that reseller and can narrow the result to one customer with `userId`. Paging defaults to 100 items per page, which is also the maximum. `pagination.total` is a real count of every chatbot matching the request, produced by a separa","read_only":true},{"name":"create_chatbot","title":"Create a chatbot","description":"Create a chatbot\n\nCreates a chatbot and provisions it in the voice engine in the same request, then derives its hosted chat page URL from the new identifier. Only `name` is required; the language defaults to `de` and the widget appearance fields all have platform defaults. The widget microphone stays off until `enableVoice` is true; a spoken conversation then runs on the voice allowance of the acc","read_only":false},{"name":"get_chatbot","title":"Get a chatbot","description":"Get a chatbot\n\nReturns the full public configuration of one chatbot, including the system prompt, the widget appearance, the widget voice, the embedding restrictions and the retention settings. `allowedDomains` and `supportedLanguages` come back as arrays, or as null when nothing is configured. Internal voice engine identifiers are never included. A reseller key may read any chatbot belonging to t","read_only":true},{"name":"update_chatbot","title":"Update a chatbot","description":"Update a chatbot\n\nChanges one or more fields on a chatbot. Every field is optional, but the body must contain at least one recognised field: an empty object is rejected with 400. `enableVoice` switches the widget microphone, `voiceId` changes the voice and an empty `voiceId` returns to the engine default; the chosen voice is kept while the microphone is off. The older `textOnlyMode` is still read ","read_only":false},{"name":"delete_chatbot","title":"Delete a chatbot","description":"IRREVERSIBLE: Delete a chatbot\n\nDeletes a chatbot permanently and removes it from the voice engine. This cannot be undone, and any widget still embedded on a website stops working. Its integration links and knowledge entries are deleted with it, and so are the indexed knowledge documents that no other agent uses. The removal in the voice engine is attempted first, but a failure there does not stop","read_only":false},{"name":"list_chatbot_integrations","title":"List integrations assigned to a chatbot","description":"List integrations assigned to a chatbot\n\nReturns every integration currently assigned to this chatbot, together with the tools it may call through them. The `enabledTools` field decides which of the integration actions the assistant may call: null means the recommended default set for that integration type, an empty array means the assistant may call nothing, and a list of tool names means exactly","read_only":true},{"name":"assign_chatbot_integration","title":"Assign an integration to a chatbot","description":"Assign an integration to a chatbot\n\nGives a chatbot access to one integration, so its tools become callable during a chat. The integration must belong to the account that owns the chatbot, which for a reseller key is the customer account, not the reseller. The `enabledTools` field decides which of the integration actions the assistant may call: null means the recommended default set for that integ","read_only":false},{"name":"update_chatbot_integration_tools","title":"Change the tool selection for a chatbot integration","description":"Change the tool selection for a chatbot integration\n\nReplaces the tool selection for one integration already assigned to a chatbot. The `enabledTools` field decides which of the integration actions the assistant may call: null means the recommended default set for that integration type, an empty array means the assistant may call nothing, and a list of tool names means exactly those tools and no o","read_only":false},{"name":"remove_chatbot_integration","title":"Remove an integration from a chatbot","description":"IRREVERSIBLE: Remove an integration from a chatbot\n\nUnassigns an integration from a chatbot, so the chatbot can no longer call any of its tools. The integration itself is untouched and stays available to assign elsewhere. The reduced tool set is pushed to the voice engine after the row is removed; if that push fails the request returns 502 and the integration is already unassigned locally but may ","read_only":false},{"name":"list_chatbot_knowledge","title":"List chatbot knowledge sources","description":"List chatbot knowledge sources\n\nReturns every knowledge source attached to one chatbot. Only the first 100 characters of each entry are returned, as `contentSnippet`; the full stored text is never sent by this endpoint. The response is a plain list with no paging. Entries belong to the account that owns the chatbot, so a reseller key that reads a customer chatbot sees the same entries as the custo","read_only":true},{"name":"add_chatbot_knowledge","title":"Add a knowledge source to a chatbot","description":"Add a knowledge source to a chatbot\n\nAdds one knowledge source to a chatbot. `type` says how to read `content`: for `url` it is the address to draw from, read again every `syncInterval` (weekly by default), for `text` it is the literal text, for `file` it is the text of the file, named by `fileName` and described by `mimeType`, and for `crawl` it is the start page of a website that is read up to `","read_only":false},{"name":"delete_chatbot_knowledge","title":"Delete a chatbot knowledge source","description":"IRREVERSIBLE: Delete a chatbot knowledge source\n\nRemoves one knowledge source from a chatbot: the entry is deleted and the chatbot no longer draws on the document. The indexed document is deleted from the voice engine as well, unless another entry or another agent still uses it. The chatbot must be one the key may use and the entry must belong to this chatbot, otherwise the request is rejected wit","read_only":false},{"name":"refresh_chatbot_knowledge","title":"Refresh a chatbot knowledge source","description":"Refresh a chatbot knowledge source\n\nRe-reads a URL knowledge source from its source page immediately and replaces the stored content with what the page says now. Website sources are also re-read on a schedule, so this is for the case where a page changed and the chatbot should know about it at once. Only entries of type `url` can be refreshed; text and file entries are rejected with 400. The entry","read_only":false},{"name":"list_phone_numbers","title":"List phone numbers","description":"List phone numbers\n\nReturns the phone numbers the account rents, newest purchase first. Wholesale costs, carrier identifiers and SIP credentials are never included, only the columns of the PhoneNumber schema. A reseller key sees every number belonging to its own customers and can narrow the result to one customer with `userId`; a direct account key ignores `userId` and always sees only its own num","read_only":true},{"name":"list_phone_number_countries","title":"List purchasable countries","description":"List purchasable countries\n\nReturns every country whose numbers can currently be bought through the number marketplace. Use the `iso` field of an entry as the `countryIso` argument of the number search and of a purchase. The list is read live from the marketplace and is not paginated. When the marketplace is not enabled for this deployment the endpoint answers 503 instead of an empty list.","read_only":true},{"name":"search_phone_numbers","title":"Search available numbers","description":"Search available numbers\n\nSearches the number marketplace for numbers that can be bought right now in one country. Nothing is reserved: a listing can disappear between the search and the purchase, so buy promptly and be ready to retry with a different result. Each entry carries the prices, the capabilities and the identifiers a purchase needs, and should be passed back to the purchase endpoint unc","read_only":true},{"name":"purchase_phone_number","title":"Purchase a phone number","description":"COSTS MONEY: Purchase a phone number\n\nBuys one of the numbers returned by the search and attaches it to the account. Buying numbers needs an active Voice subscription (Voice, Bundle or a voice capable plan) and is not possible during the free trial; otherwise the request is rejected with 403 and one of the codes `voice_subscription_required`, `voice_subscription_inactive` or `trial_not_allowed`, b","read_only":false},{"name":"get_phone_number","title":"Get a phone number","description":"Get a phone number\n\nReturns one phone number of the account. The response is the PhoneNumber object itself, not wrapped in a `data` envelope. Use it to read the current assignment, the lifecycle status and the regulatory verification state of a number. A number that does not belong to the calling account answers 404 rather than 403.","read_only":true},{"name":"update_phone_number","title":"Update a phone number","description":"Update a phone number\n\nChanges which agent answers on a number and the label it carries in the dashboard. Only the fields present in the body are written, everything else is left alone; a body with no known field is rejected with 400. The response is an acknowledgement message only, it does not echo the updated record: read the number back with the GET endpoint if you need the new state. Assigning","read_only":false},{"name":"cancel_phone_number","title":"Cancel a phone number","description":"IRREVERSIBLE: Cancel a phone number\n\nCancels a number bought through the marketplace, with a 30 day grace period: the number is released at the carrier straight away but stays usable on the account until `cancelationEndDate`, and the record is kept rather than deleted. Only marketplace numbers can be cancelled here; a number that was imported by other means is rejected with 400. Cancelling twice i","read_only":false},{"name":"get_phone_number_verification","title":"Get the verification requirement","description":"Get the verification requirement\n\nReturns what the regulator demands before this number can carry traffic. When the number needs no verification the response is `{ \"kycRequired\": false, \"requirement\": null }`. Otherwise `requirement` describes the accepted identity kinds, how many documents of which type are needed, which fields are mandatory and which forms must be signed. Read this first: it tel","read_only":true},{"name":"submit_phone_number_verification","title":"Submit verification","description":"Submit verification\n\nSubmits the identity, address and document proofs demanded for a regulated number. Upload the document files first and pass their identifiers in `proofs`; which document types are accepted and how many are needed comes from the requirement endpoint. The submission is forwarded to the registry and the number moves to the `pending` verification state, from where the status endpo","read_only":false},{"name":"get_phone_number_verification_status","title":"Get verification status","description":"Get verification status\n\nPolls the current state of the regulatory verification for a number. Once a submission exists the state is read live from the registry and the stored value on the number record is updated to match, so this endpoint is what to poll after submitting. Before any submission it answers `not_submitted` for a number that needs verification, and the number's recorded state, normal","read_only":true},{"name":"list_conversations","title":"List conversations","description":"List conversations\n\nReturns a page of conversations, newest first. One `type` is listed at a time: `voice` returns call records and `chat` returns widget and WhatsApp threads. Every item carries a `type` field so a client can tell the two shapes apart without remembering which query it sent. The pagination object reports `page`, `perPage`, the `type` that was listed and `total`, a real count of th","read_only":true},{"name":"get_conversation","title":"Get a conversation","description":"Get a conversation\n\nReturns one conversation. The `type` query parameter selects which store the id is looked up in and must match the kind of record you are asking for, since voice calls and chat threads number themselves independently. A voice call is returned on its own. A chat conversation is returned together with its full transcript in `messages`, ordered oldest first and not paginated; for ","read_only":true},{"name":"update_conversation","title":"Update a chat conversation","description":"Update a chat conversation\n\nChanges the status, the archive flag or the assigned human agent of a chat conversation. Chat threads only: an id belonging to a voice call is rejected with 400, and a body with no updatable field is rejected with 400 as well. Assigning an agent also stamps the assignment time and, unless the same request sets a status, moves the thread to `active`, mirroring what the d","read_only":false},{"name":"list_conversation_messages","title":"List conversation messages","description":"List conversation messages\n\nReturns a page of the transcript of a chat conversation, oldest message first, so paging forward follows the conversation in order. This endpoint serves chat threads only: an id that belongs to a voice call is rejected with 400 rather than a misleading 404, and the transcript of a call is carried on the call record itself. Unlike the conversation list, the pagination ob","read_only":true},{"name":"send_conversation_message","title":"Reply in a conversation","description":"Reply in a conversation\n\nSends a message into a chat conversation as a human agent, delivering it to the visitor over the same channel the thread runs on. An API key is not itself an agent session, so the message is attributed to the agent already assigned to the thread, or to the account's first live chat agent when it is unassigned. An account with no live chat agent at all cannot send and is re","read_only":false},{"name":"close_conversation","title":"Close a chat conversation","description":"IRREVERSIBLE: Close a chat conversation\n\nCloses a chat conversation and finalises it: the closing time is stamped and the response time and duration figures of the thread are recomputed, which is what the analytics endpoints then report. Chat threads only, a voice call id is rejected with 400. This endpoint takes no request body. Closing an already closed conversation runs the finalisation again r","read_only":false},{"name":"get_analytics_summary","title":"Get a usage summary","description":"Get a usage summary\n\nReturns usage over a date window, aggregated into one row per usage type, with the quantity consumed and the revenue, cost and margin that go with it. Rows appear only for usage types that were actually recorded in the window, so an idle account gets an empty `metrics` array rather than rows of zeroes. Both bounds are optional: without them the window is the last 30 days endin","read_only":true},{"name":"get_daily_analytics","title":"Get daily call metrics","description":"Get daily call metrics\n\nReturns one row of metrics per calendar day, oldest day first, ready to plot as a time series. The figures are read live from the conversation records, so a conversation is counted as soon as it has ended, and the voice calls, chat sessions and avatar sessions of the account each count as one call. Cost is in USD, as the voice engine reports it. Days with no activity are ab","read_only":true},{"name":"get_agent_analytics","title":"Get agent statistics","description":"Get agent statistics\n\nReturns the lifetime aggregate metrics of one voice agent: call counts, durations, cost, token consumption and quality scores. The figures are read live from the conversation records, so a call is counted as soon as it has ended. Cost is in USD, as the voice engine reports it. An agent that exists but has no recorded activity yet answers 200 with `stats` set to null. An agent","read_only":true},{"name":"get_chatbot_analytics","title":"Get chatbot statistics","description":"Get chatbot statistics\n\nReturns the lifetime aggregate metrics of one chatbot: session counts, durations, cost, token consumption and quality scores. The figures are read live from the conversation records and count a chat session and a spoken widget conversation alike, so the fields are named after calls even though most entries are chat sessions; the two call-length extremes tracked for voice ag","read_only":true},{"name":"list_webhooks","title":"List your webhook endpoints","description":"List your webhook endpoints\n\nReturns every outbound webhook endpoint registered by the account, newest first and unpaged. The signing secret is not part of this response and cannot be read back at any point: it is shown once, when the endpoint is created. Use `failedDeliveries`, `lastDeliveryAt` and `lastDeliveryStatus` to spot an endpoint that has started rejecting deliveries before it is switche","read_only":true},{"name":"create_webhook","title":"Register a webhook endpoint","description":"Register a webhook endpoint\n\nRegisters an HTTPS endpoint and subscribes it to the named events. The response contains a `secret`, and this is the only time it is ever returned: store it before you do anything else, because no endpoint anywhere in this API will show it to you again, and losing it means deleting the endpoint and registering a new one. The secret keys the HMAC-SHA256 signature sent w","read_only":false},{"name":"list_webhook_events","title":"List the events you can subscribe to","description":"List the events you can subscribe to\n\nReturns the catalogue of outbound events with a one-line explanation of when each is emitted. These names, plus the wildcard returned in `wildcard`, are the only values accepted in the `events` list when creating or updating an endpoint. `webhook.test` appears in the catalogue but is never produced by platform activity: it is only sent when you ask for a test ","read_only":true},{"name":"get_webhook","title":"Read one webhook endpoint","description":"Read one webhook endpoint\n\nReturns a single registered endpoint, wrapped in a `data` object. The signing secret is not included and cannot be recovered here or anywhere else. Note `isActive` together with `failedDeliveries`: an endpoint is disabled automatically once 25 consecutive deliveries have failed, and a single successful delivery resets that counter to zero.","read_only":true},{"name":"update_webhook","title":"Update a webhook endpoint","description":"Update a webhook endpoint\n\nChanges the destination URL, the subscription list or the enabled flag of an endpoint. Every field is optional and only the fields you send are touched. `events` is replaced wholesale, not merged, so send the complete list you want; each name is checked against the catalogue and an unknown one fails the whole request with 400. A new URL is resolved and refused if it poin","read_only":false},{"name":"delete_webhook","title":"Delete a webhook endpoint","description":"IRREVERSIBLE: Delete a webhook endpoint\n\nRemoves an endpoint permanently. Deliveries stop at once and the signing secret is destroyed with the record, so this cannot be undone: registering the same URL again produces a new endpoint with a new secret. If you only want to pause deliveries, set `isActive` to false with a PATCH instead.","read_only":false},{"name":"test_webhook","title":"Send a test delivery","description":"Send a test delivery\n\nSends one signed `webhook.test` payload to the endpoint and reports what happened, synchronously and with no retry. This is a real delivery: it is signed with the endpoint's secret, so it is the right way to check your signature verification. It updates `lastDeliveryAt` and `lastDeliveryStatus` and nothing else: a failed test never counts towards the automatic disabling that ","read_only":false},{"name":"list_tickets","title":"List support tickets","description":"List support tickets\n\nReturns the account's support tickets, newest first, with no paging. By default only open work is listed: tickets in state `closed` or `resolved` are left out unless you ask for them. Pass `includeArchived=true` to get exactly the closed and resolved ones instead, or `status` to filter to a single state. `includeArchived` takes precedence over `status` when both are sent. Nei","read_only":true},{"name":"create_ticket","title":"Open a support ticket","description":"Open a support ticket\n\nCreates a support ticket on behalf of the authenticated account and returns its identifier. The ticket starts in state `open`, and `category` and `priority` fall back to `other` and `medium` when they are not given. Put everything a human needs into `description`: error messages, the identifiers involved and the steps that led to the problem, since the first reply is written","read_only":false},{"name":"get_ticket","title":"Read a ticket and its thread","description":"Read a ticket and its thread\n\nReturns one ticket with its full public message thread, oldest message first. Internal notes written by staff for staff are filtered out and never appear here, so the thread you see is the correspondence you took part in. Each message carries the sender's display name and role. `System` is used where a message was generated by the platform rather than typed by a perso","read_only":true},{"name":"reply_to_ticket","title":"Reply to a ticket","description":"Reply to a ticket\n\nAdds a public reply to an existing ticket and bumps its last-changed timestamp, which is what moves the ticket back up the support queue. A ticket in state `closed` cannot be replied to and returns 400; a resolved ticket still accepts replies, so use this to reopen a conversation that was closed too early. Attachments are referenced by URL, they are not uploaded here: host the f","read_only":false},{"name":"list_bookings","title":"List the bookings in your connected calendars","description":"List the bookings in your connected calendars\n\nReturns the bookings of every active integration that has a calendar (Cal.com, Calendly, Google Calendar, Outlook), sorted by start, or of one integration when you pass `integrationId`. Each booking carries the `id` that the confirm, decline and cancel paths take. Bookings are read live from the calendar provider on every request, so poll at a calm pa","read_only":true},{"name":"list_integration_event_types","title":"List the event types of a calendar integration","description":"List the event types of a calendar integration\n\nReturns the kinds of appointment that can be booked through this integration, read live from the calendar provider: their name, their duration in minutes and their identifier. An empty list means the calendar has no event types; a provider that cannot be reached or refuses is answered with 502 `provider_error`, not with an empty list.","read_only":true},{"name":"confirm_booking","title":"Confirm a booking request","description":"Confirm a booking request\n\nConfirms a booking that waits for the host (status `pending`). The calendar provider then informs the attendee as it always does. Only calendars with booking requests support this (Cal.com). The others answer 422 `not_supported`.","read_only":false},{"name":"decline_booking","title":"Decline a booking request","description":"IRREVERSIBLE: Decline a booking request\n\nDeclines a booking that waits for the host (status `pending`). The optional `reason` is handed to the calendar provider, which may show it to the attendee. Only calendars with booking requests support this (Cal.com). The others answer 422 `not_supported`.","read_only":false},{"name":"cancel_booking","title":"Cancel a booking","description":"IRREVERSIBLE: Cancel a booking\n\nCancels a booking in the calendar of the integration. The optional `reason` is handed to the calendar provider, which may show it to the attendee.","read_only":false},{"name":"list_integration_types","title":"List the integration types you can connect","description":"List the integration types you can connect\n\nReturns the catalogue of supported third-party services, each with the configuration fields it needs. Read this before creating an integration: `type` gives you the value to send, and `configFields` tells you exactly which keys belong inside the `config` JSON string and which of them are required. Fields declared with type `password` are masked when the ","read_only":true},{"name":"list_integrations","title":"List your integrations","description":"List your integrations\n\nReturns the account's connected integrations, newest first, as a bare JSON array with no paging. Stored configuration is deliberately left out of the list view: read a single integration to see which of its fields are set. A reseller key may pass `userId` to list one of its own customers' integrations instead; asking for a user who is not a customer of that reseller is refu","read_only":true},{"name":"create_integration","title":"Connect an integration","description":"Connect an integration\n\nStores the credentials and settings for one third-party service and returns the new integration's identifier. The integration is created active, but connecting it does not by itself let an agent use it: it still has to be assigned to an agent or chatbot. `config` is a JSON string, not a nested object, so serialise it before sending; the keys it must contain are the ones lis","read_only":false},{"name":"get_integration","title":"Read one integration","description":"Read one integration\n\nReturns a single integration including its stored `config`, with every secret value replaced by `********`. A value counts as secret when its field is declared with type `password` for the integration type, when its key contains `secret`, `password`, `passwd`, `token`, `apiKey`, `api_key`, `authorization`, `authValue`, `credential`, `bearer` or `cookie` or ends in `Key` (case","read_only":true},{"name":"update_integration","title":"Update an integration","description":"Update an integration\n\nChanges the name, description, stored configuration or enabled flag of an integration. Only the fields you send are written. A `config` you send is merged with the stored one, one object level at a time. A field that is not secret takes the value you send, and one you leave out is removed, so send every non-secret field you want to keep. A secret field keeps its stored value","read_only":false},{"name":"delete_integration","title":"Delete an integration","description":"IRREVERSIBLE: Delete an integration\n\nRemoves the integration and the credentials stored with it. When an account of the service was connected through the dashboard for this integration, that connection is removed as well, unless another integration still uses it; this happens on a best-effort basis and never blocks the delete. This cannot be undone, and any agent that was assigned this integration","read_only":false},{"name":"list_integration_tools","title":"List the tools an integration offers","description":"List the tools an integration offers\n\nReturns the actions an agent can be allowed to perform through this integration, plus the recommended default selection in `recommended`. Only a few integration types are catalogue-backed; the rest have a fixed tool set that cannot be picked from and answer 404 here, with the same status used for an integration that does not exist or belongs to someone else. N","read_only":true},{"name":"get_integration_permissions","title":"Read the tool permissions of an integration","description":"Read the tool permissions of an integration\n\nReturns which tools the agents of the account may use through this integration: the stored choice in `preset`, every tool of the integration with `allowed`, and how many tools each preset would allow. The permissions limit agents only; the account owner keeps full access through the dashboard and the calendar endpoints. Only Genesys Cloud and the integr","read_only":true},{"name":"set_integration_permissions","title":"Set the tool permissions of an integration","description":"Set the tool permissions of an integration\n\nStores which tools the agents of the account may use through this integration, exactly as the dashboard does. Choose a preset (`read`, `read_write`, `full`) or `custom` with the exact tool keys from `tools[].key` of the GET of this path. Only the permissions change; the rest of the stored configuration stays as it is. Every agent and chatbot the integrat","read_only":false},{"name":"test_integration","title":"Test an integration","description":"Test an integration\n\nCalls the connected service with the stored credentials and reports what came back. Use it after creating or reconfiguring an integration, since nothing is verified at write time. The shape of the result depends on the integration type: each connector builds its own diagnostic payload, so read it as free-form JSON rather than a fixed schema, and expect at least an indication o","read_only":false},{"name":"get_my_account","title":"Get the current account profile","description":"Get the current account profile\n\nReturns the account that the presented API key belongs to, which is the simplest way to confirm a key is valid and to discover the user id every other endpoint scopes to. `resellerId` is set when this account is a customer of a reseller, and `ownResellerId` is set when the account operates a reseller itself; both are null for a plain direct account. `avatarUrl` is ","read_only":true},{"name":"update_profile","title":"Change your profile name","description":"Change your profile name\n\nChanges the name of your account, the `name` that `get_my_account` returns. It applies at once and can be changed back the same way. Only the name changes here: the email address can only be changed by support (ask with `create_ticket`), the invoice address is set with `set_billing_address`. Only the account owner can call this; a team member gets 403.","read_only":false},{"name":"get_my_usage","title":"Get consumption for a date window","description":"Get consumption for a date window\n\nSums the metered consumption recorded for this account over a date window, broken down into voice minutes and chat sessions. With no query parameters the window runs from midnight on the first day of the current month in server local time up to the moment of the request, which makes the bare call a current-month total. Both bounds are inclusive. The two counters ","read_only":true},{"name":"get_my_limits","title":"Get plan allowances and remaining credit","description":"Get plan allowances and remaining credit\n\nReturns what the account still has available: its status, its prepaid wallet balance in EUR, the voice minutes and chat conversations left, and the subscribed plan with its monthly allowances. `plan` is null when the account is on no plan, in which case the remaining counters are whatever credit has been granted directly. Poll this before starting a batch ","read_only":true},{"name":"list_languages","title":"List available interface locales","description":"List available interface locales\n\nReturns the user interface locales the platform ships, for populating a language picker or for validating a value before writing it to a profile or an agent. The list is read from the locale directories on disk, so it reflects the running build rather than a database table; reseller-specific locale folders are excluded. If that directory cannot be read the handler","read_only":true},{"name":"list_agent_languages","title":"List the languages an agent can speak or write","description":"List the languages an agent can speak or write\n\nReturns the languages you can assign to an agent, each with an English name, the name the language calls itself, and a region code for a flag image, so a language picker needs no table of its own. This is a different list from `GET /languages`, which returns the locales the dashboard interface is translated into. Populating an agent picker from the l","read_only":true},{"name":"list_notifications","title":"List account notifications","description":"List account notifications\n\nReturns the notification inbox of the account behind the API key, newest first by creation time. Notifications are raised by the platform for events such as ticket replies or billing changes, and each entry may point at the resource that caused it through `relatedType` and `relatedId`. Pass `unreadOnly=true` to see only unread entries: the handler compares the raw query","read_only":true}],"server_info":{"name":"echocall","title":"EchoCall","version":"1.23.0"},"category":"automation","tags":["agents","communication","research"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-11-07","stars":0,"badges":["new"],"sponsor":null,"page":"https://agentsindex.org/agents/de-echocall-echocall/"}