Nothing breaks
Every earlier path keeps working exactly as before. They are no longer listed in the reference and are marked deprecated, but they accept the same requests and return the same responses. You do not have to change an integration to keep it running. Move to the merged endpoints when you next touch the code.What changed in how you call the API
- List and get are one call.
GET /leadslists leads; passidfor one lead with everything attached to it. The same goes for lead lists, campaigns, agents, knowledge bases, tools, widgets, calls, webhook endpoints, jobs and conversations. - Settings are fields on the update call. A lead’s tags, stage and traffic light are on
PATCH /leads/{lead_id}. A campaign’s status and enrolled leads are onPATCH /campaigns/{campaign_id}. An agent’s channels, inbound settings, knowledge bases, tools and publish state are onPATCH /agents/{agent_id}. - One call can run several steps. Steps run in a fixed order. If one fails, the steps before it stay applied and the error lists them under
applied. Read the resource before you repeat the call. - Some paths are new. Voice agents are
/agents, calls are/calls, widgets are/widgets, and messages arePOST /messages.
Where each earlier endpoint went
Find the request you use today in the left column. The right column is the merged endpoint; the guide for each area shows the exact fields.Leads
Campaigns
Conversations
Agents
Calls and numbers
Platform
Agency
Left out of the reference
These still work. They are not part of the reference because they are repeated by another endpoint, or are called by Sendora’s own app or embed script rather than by your server.Merged again: one set of calls per family
A second pass merged similar resources behind atype field. Each family has GET (list or read), POST (create), PATCH /{id}, DELETE /{id}?type= and POST /{id}/actions. The earlier paths keep working.