Async API to send call personalisation data for a Caller-Receiver combination
Here are a few things to consider when pushing the records through the API :-
Caller and receiver should be phone numbers without the “+” character.
ends_at should not be before the current timestamp.
starts_at and ends_at cannot be more than 24 hrs apart
label_id should be that of a dynamic label belonging to this client.
Label name and call reason are optional fields.
Max length for label name is 40 chars
Min length for call reason is 10 chars
Max length for call reason is 100 chars
starts_at and ends_at should be in milliseconds.
Truecaller for Business restricts API requests when you exceed the limits entitled to your business.
Thus, if your business is using a batch based approach to push records to our systems, 10*60*500 = 300000 records can be processed every minute.
Here, the batch size is 500. This means that a maximum of 500 requests can be processed at a time.
Exponential Backoff: If you receive a "429" status code, consider implementing exponential backoff for retrying requests.
Prioritize Important Requests: If your application performs various tasks, prioritize critical requests over less essential ones to stay within limits.
This endpoint pushes the dynamic caller ID details to the respective TC users. It supports batching. Maximum batch size is 500
This should be the clientAccountId
"application/vnd.api+json; version=1.0"The call reason to be displayed.
The phone no. of the caller
The timestamp in milliseconds at which dynamic caller ID should expire.
The label ID of the dynamic label to be used as caller id
The caller ID name to be displayed. If not present it will default to the label name of the label ID provided.
The phone no. of the receiver
The timestamp in milliseconds at which dynamic caller ID should start reflecting.