calls
Create or update a call
Syncs one call from your call-tracking vendor into Ritten's CRM.
This endpoint is idempotent: a call is identified by its provider and externalId, and resubmitting the same pair replaces the stored call in full with the payload you send. Send the complete record every time — retries and corrected re-sends are always safe, and there is no separate update endpoint. Both create and replace return 200 with the stored record.
Two consequences of full-record replace to be aware of:
- Omitting an optional field (campaign, note) clears any value stored by an earlier send.
- Staff-made changes in Ritten (linking the call to a case) are never touched by this endpoint.
post/calls
Request
- Base URL: https://api.ritten.io/v1
- URL: https://api.ritten.io/v1/calls
- Auth: none declared
Request body
Example request
{
"provider": "ringcentral",
"externalId": "rec-8842613",
"calledAt": "2024-01-15T14:32:00Z",
"callerName": "Jane Doe",
"direction": "inbound",
"phoneNumber": "+15551234567",
"durationSeconds": 142,
"campaign": "Google Ads",
"note": "Caller asked about admission availability."
}Response
Call created or replaced successfully. The stored record is returned in both cases.
Example response
{
"id": "182c2e54-3494-4b85-aba5-038cf539d5bf",
"provider": "ringcentral",
"externalId": "rec-8842613",
"callerName": "Jane Doe",
"phoneNumber": "+15551234567",
"durationSeconds": 142,
"calledAt": "2024-01-15T14:32:00Z",
"campaign": "Google Ads",
"note": "Caller asked about admission availability.",
"createdAt": "2024-01-15T14:35:00Z"
}Changes
No recorded changes to this operation across all 1 revision of this API.