Create Account
Recent search
Bulk Call Details - API Console
Advanced Search
235 results found
Receive RCS Incoming Message
API
RCS Status Callback
Send RCS Template Message
Receive Outbound Call Notifications
WhatsApp Error Code
https://<your_api_key>:<your_api_token><subdomain>/v1/Accounts/<your_sid>/Calls Copy
To get details of calls in bulk (including Status, Price, etc.), you will need to make a HTTP GET request to
string; an alpha-numeric unique identifier of the call
One or multiple Call SIDs which are comma separated. Recommended limit of SIDs which should be passed together is 20 and maximum allowed limit is 100. If DateCreated is not set, it will only check for last 31 days by default. While querying Sid(s) older than 31 days, DateCreated filter needs to be provided.
Example: /Calls?Sid=48d690c837bb0c755a1228dcb6911416,d7d9cefd9773dd746d8f1e029cdb1417 /Calls?Sid=48d690c837bb0c755a1228dcb6911416&DateCreated=gte:2019-01-01 00:00:00;lte:2019-01-31 23:59:59
Date and time at which the Call resource was created in the Exotel system. Supported operators (gte and lte), for more info refer to filter operators section below. You can query call records only up to 6 months old and provide maximum date range of 1 month.
Default if not set: Last 31 days
Example: /Calls?DateCreated=gte:2019-01-01 00:00:00;lte:2019-01-31 23:59:59
Your customer’s phone number. One or multiple To numbers can be provided (in E.164 format) which are comma separated. (max limit: 5)
Example: /Calls?To=<number-1> /Calls?To=<number-1>,<number-2>”
The phone number that will be called first. One or multiple From numbers can be provided (in E.164 format) which are comma separated. (max limit: 5)
Example: /Calls?From=<number-1> /Calls?From=<number-1>,<number-2>,…
Overall call status, which could be one of:
queued – The call is ready and waiting in line before going out
ringing – The call is currently in-flight
in-progress – The call was answered and is currently in progress
completed – The call was answered and has ended normally
failed – The call could not be completed as dialled, most likely because the phone number was non-existent
busy – The caller received a busy signal
no-answer – The call ended without being answered
Example: /Calls?Status=completed /Calls?Status=failed,no-answer,busy,canceled
Call duration in seconds. Supported operators (gte, eq and lte), for more info refer to filter operators section below.
Example: /Calls?Duration=gte:10s;lte:45s /Calls?Duration=eq:30s
If present, this will be the amount (as per your billing currency) you have been charged for the call. Supported operators (gte, eq and lte), for more info refer to filter operators section below.
Example: /Calls?Price=gte:0.10;lte:1.0 /Calls?Price=eq:0.300030
inbound
outbound-dial – Outbound calls from Exotel dashboard
outbound-api – All other Outbound calls (API, campaign etc.)
Example: /Calls?Direction=inbound /Calls?Direction=outbound-dial,inbound
This represents the Virtual Number (ExoPhone) used for the call. One or multiple PhoneNumber(s) can be provided (in E.164 format) which are comma separated. (max limit: 5)
Example: /Calls?PhoneNumber=<vn-1> /Calls?PhoneNumber=<vn-1>,<vn-2>,…
This represents number of records visible in one page of the API response. Default: 50, Max: 100
This indicates in what order the Call records are sorted in the API response. By default records are sorted by DateCreated in descending order. However, you can override the same in following way for ascending order:
Example: /Calls?SortBy=DateCreated:asc
Auto generated unique string returned in the PrevPageUri (under Metadata) to be used as query param when at least one record is returned in that page. The value of this field is a cursor which identifies a call record uniquely.
Auto generated unique string returned in the NextPageUri (under Metadata) to be used as query param when at least one record is present in that page. The value of this field is a cursor which identifies a call record uniquely.