Submit and follow work
Upload audio, retain the returned Note ID, and poll asynchronous processing until success or a documented terminal failure.
Audream REST API
Use revocable API keys from Audream Settings in trusted server-side applications and automations.
WHAT THE PLATFORM COVERS
Upload audio, retain the returned Note ID, and poll asynchronous processing until success or a documented terminal failure.
Retrieve processed Notes, transcript content, structured Insights, and generated artifacts from one contract.
Ask a grounded workspace question and preserve the supporting Note IDs returned with the answer.
API keys are shown once, stored as hashes by Audream, and should never be embedded in mobile apps, browsers, or firmware.
START WITH A REAL WORKFLOW
Follow the published authentication boundary for this interface. Keep credentials out of browsers, mobile apps, firmware, logs, and source control.
export AUDREAM_API_KEY="audream_sk_..."
curl --fail-with-body \
--header "Authorization: Bearer $AUDREAM_API_KEY" \
https://audream-api.tulingbc.com/v1/accountIMPLEMENTATION BOUNDARIES
Send the API key as a bearer token from a trusted runtime. Key creation is an authenticated account action, not a public OpenAPI operation.
Treat 202 Accepted, queued, and processing as incomplete. Poll with a bounded retry policy and preserve documented terminal errors.
Generated results and complete Notes have separate delete operations. Confirm the exact target and user intent immediately before a permanent delete.
The detailed contract, current installation steps, scopes, and operation schemas remain in the versioned Audream documentation.
Open the complete documentation ↗DELIVERY
KEEP EXPLORING
A PRODUCT, NOT A PILE OF PARTS