Skip to main content
This endpoint returns a paginated list of call recordings associated with your Shilo organization. Only non-roleplay calls are returned. You can narrow results using filters for the owning agent, associated contact, sales stage, recording source, or creation date range. Results are returned in cursor-based pages to support efficient traversal of large datasets.

Endpoint

Query Parameters

number
Maximum number of call records to return in a single page. Defaults to 50. Maximum allowed value is 100.
string
Opaque pagination cursor returned as next_cursor in a previous response. Pass this value to retrieve the next page of results. Omit to start from the beginning.
string
Sort order for results by creation date. Accepts "asc" (oldest first) or "desc" (newest first). Defaults to "asc".
string
Return only calls created on or after this timestamp. Must be a valid ISO-8601 datetime string (e.g. 2030-01-01T00:00:00Z).
string
Return only calls created on or before this timestamp. Must be a valid ISO-8601 datetime string. Use together with created_date_gte to define a date range.
string
Filter calls by their recording source ID. Corresponds to source_id on the Call object.
string
Filter calls by the agent who owns them. Supports three formats:
  • {uuid} — Shilo User UUID directly
  • id:{uuid} — explicit Shilo UUID prefix
  • external_user_id:{value} — your own system’s agent identifier
string
Filter calls by the associated contact. Supports three formats:
  • {uuid} — Shilo Contact UUID directly
  • id:{uuid} — explicit Shilo UUID prefix
  • external_contact_id:{value} — your own system’s contact identifier
string
Filter calls by the sales stage ID associated with the contact at the time of the call.

Response

A successful request returns HTTP 200 with a CallsResponseDto object containing a data array of Call objects and a pagination object.
array
Array of Call objects matching the query.
object
Pagination metadata for iterating through large result sets.

Example Response

Example Request

Error Responses

401 Unauthorized — Returned when the API key is missing or invalid. Missing x-api-key (or Authorization: Bearer) header:
Unrecognized or revoked key: