Skip to main content
GET
Get audio recording for a conversation

PII access and redaction

The redacted query parameter controls whether personally identifiable information (PII) is muted from the returned audio: Users without PII access always receive the redacted recording, even when redacted=false is passed. This is enforced server-side, so callers cannot bypass redaction by omitting or overriding the query parameter. PII access is granted through your account’s role and permission configuration in Agent Studio. See PII logging for related conversation-log behavior.

Regional base URLs

This endpoint is served from the Kong-routed host (api.{region}.poly.ai), not api.{region}-1.platform.polyai.app (which serves the list-conversations endpoint). Sending the request to the wrong host will fail.

Example

Replace {agentId} and {conversationId} with real values — the placeholders are not resolved server-side. Only Accept: audio/wav is needed; do not send Content-Type on this GET request (it has no body).

Common pitfalls

Authorizations

X-API-KEY
string
header
required

Path Parameters

agentId
string
required
conversationId
string
required

Query Parameters

direction
enum<string>
default:combined

Audio direction: "combined", "user", or "agent"

Available options:
combined,
user,
agent
redacted
boolean
default:false

Whether to return redacted audio

Response

Successful response

The response is of type file.

Last modified on June 1, 2026