Ambient Content Retrieval
Get Ambient Session Status
Check current status and processing state of Ambient session
GET
cURL
Use this endpoint to get the current status of an . Use it to track the session’s progress, for example, to see if it is ready to receive audio, still processing, or has completed.
Session status values
Use the following status values to track the session’s progress:- created: The ambient session has been created but has not yet started.
- ready: The ambient session has started and is ready for audio streaming.
- running: The ambient session is actively processing audio and generating content.
- aborted: The ambient session has been cancelled by the user or client.
- skipped: The ambient session was skipped because not enough audio was received or the was empty.
- failed: The ambient session failed due to an error during processing.
- completed: The ambient session completed successfully and generated the final content.
Code examples
- Python
- TypeScript
Authorizations
Suki access token (suki_token) from Login or Register. Expires after one hour.
Headers
Optional for standard partners.
Required for:
- Bearer authentication. Use the same
provider_idreturned by the Login or Register API. - Single Auth Token authentication. Include the same
provider_idon every request assdp_provider_id.
Example:
"provider-123"
Path Parameters
UUID for the ambient session. Use the ambient_session_id returned from Create Ambient Session, or the UUID you supplied in that request.
Response
Request succeeded.
Current processing status for an ambient session.
Processing state of the ambient session. Poll until the status is completed, failed, or aborted.
Available options:
created, ready, running, paused, aborted, failed, completed Example:
"completed"
Last modified on July 23, 2026
cURL