RillaRilladevelopers
Go to Rilla
DocumentationData Export APIFull reference

Export teams

Export team conversation, coaching, engagement, and recording compliance metrics.

POST/export/teams
Authentication
Authorization: YOUR_API_KEY

No Bearer prefix.

Base URL: https://customer.rillavoice.com

Body parameters

fromDatestring · date-timerequired

Start of the export window. Use an ISO 8601 timestamp in UTC, such as 2026-09-01T00:00:00Z.

toDatestring · date-timerequired

End of the export window. Use a UTC timestamp ending in Z and a value after fromDate. See Date windows for metric-specific boundary behavior.

includeSubteamsboolean

Roll descendant-team members into each team’s metrics. Defaults to false (direct members only). This does not hide descendant team rows.

This endpoint is not paginated. Results remain restricted to the access granted to your API key.

Responses

200Returns TeamsExportResponse
teamsTeamsExport[]

One TeamsExport per selected team.

401Missing or invalid API key.
400Invalid request parameters.
Error reference

Date windows

Send UTC timestamps ending in Z; date-only values and timezone offsets are not accepted. Choose fromDate < toDate; the API does not enforce date ordering.

Conversation exports include both boundaries. Most user/team metrics do too, but scorecards and live coaching exclude the end boundary. Profile fields and current team membership are not historical snapshots.

For incremental conversation exports, overlap windows and deduplicate by conversationId or recordingId. Download audio/transcripts promptly; signed URLs expire after 6 hours and may expire sooner with the signing credentials.

Common problems

400 · "Invalid JSON in request body"

Use straight double quotes ("), not smart quotes (“ ”), and remove trailing commas. Validate the body locally with python3 -m json.tool request.json. A JSON syntax error occurs before date or email validation.

400 · "Validation failed"

Read errors[].path and errors[].message. fromDate/toDate must be UTC timestamps ending in Z. includeSubteams is a JSON boolean (true or false), not a string.

401 · Missing or invalid key

Use Authorization: YOUR_API_KEY, without Bearer. Use the key value, not its ID, and the customer.rillavoice.com host.

200 · Empty or unexpected results

Check your key’s selected teams. includeSubteams controls descendant roll-up into metrics, not which team rows are returned. Metrics use current, active, non-hidden membership.

A metric is null, zero, or differs from a dashboard

Null means no applicable measurement; zero is a numeric result. Users and teams include more than successful conversations: conversationsRecorded counts recordings. See the linked type for units, date basis and aggregation rules.

← Get a conversationExport users