Support and changelog

Where to get help with the API, what to include in a report, versioning, and where product help lives.

#Get help

Need	Where
API, MCP, webhooks or SDK question, or a bug	[email protected]
How to use the Ody app (inbox, calls, billing, settings)	Help Center (help.ody.co)
Account, plan or billing	In the app: Settings → Billing, or the chat bubble
Security issue	[email protected] with "Security" in the subject. Don't post details publicly

Including these gets you an answer much faster:

The X-Request-Id of a failing request (it's in every response header and error body).
The endpoint or MCP tool, and the time (with time zone).
Live or test key (the prefix is enough, never send the full key).
What you expected and what you got (status code and error.code).

The REST API is versioned in the path (/v1). Within v1, changes are additive: new endpoints, new optional fields, new event types and new error messages. A breaking change would ship under a new version.
Treat unknown JSON fields and unknown webhook types as normal: ignore them.
Webhook payloads carry apiVersion (currently 2026-06-01), so you can see the contract a delivery follows.
error.code values are stable; error.message wording isn't.

Date	Change
2026-10-14	Five more webhook events are live: `call.ringing`, `call.answered`, `call.forwarded`, `contact.updated`, `contact.deleted`. SDKs 0.3.0 add `parseWebhookEvent` / `parse_webhook_event` and a typed event catalog
2026-10-14	Developer docs moved to dev.ody.co (previously in the Help Center)
2026-10-08	Toll-free numbers: `type=toll_free` on number search and purchase ($10/mo, calling only)
2026-08-17	Agent Phone: buy numbers, file 10DLC, place AI calls and configure the agent via API and MCP
2026-08-16	Developer platform v2: outbound webhooks (Standard Webhooks), test keys, idempotency, cursor pagination, SDKs, `api.ody.co`
2026-07-02	Per-key scopes for the REST API and MCP server
2026-06-23	REST API and MCP server launched