Get a conversation
Retrieve a conversation by its Rilla conversation ID.
/export/conversations/{conversationId}Authorization: YOUR_API_KEYNo Bearer prefix.
Base URL: https://customer.rillavoice.com
Path parameters
conversationIdstring · uuidrequiredThe Rilla conversation ID, not the recording ID or the CRM event ID.
Returns a bare conversation object, not a pagination envelope. An unknown or out-of-scope conversation returns 404.
Responses
200Returns ConversationsExportA bare ConversationsExport object. No envelope.
401Missing or invalid API key.400Invalid request parameters.404Record not found or outside your key’s scope.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"
Use a valid UUID in conversationId. Read errors[].path and errors[].message; this GET request needs no body.
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.
404 · Conversation not found
Use the conversation ID, not recordingId or crmEventID. Check that the conversation belongs to the organization and scope of your API key.
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.