Embed Tokens
Generating tokens
Section titled “Generating tokens”POST /v1/embed/token| Field | Type | Required | Description |
|---|---|---|---|
collection_id | string | ✅ | Target collection UUID |
user_id | string | ✅ | Target user UUID |
expires_in | integer | TTL in seconds (default: 604800 / 7 days, max: 2592000 / 30 days) |
curl -X POST https://api.nouncify.com/v1/embed/token \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"collection_id": "...", "user_id": "..."}'Response 200 OK
{ "embed_token": "emb_tk_xY2mK8nP...", "embed_url": "https://embed.nouncify.com/record?token=emb_tk_xY2mK8nP...", "embed_html": "<iframe src=\"https://embed.nouncify.com/record?token=emb_tk_xY2mK8nP...\" width=\"400\" height=\"300\" frameborder=\"0\" allow=\"microphone\"></iframe>", "expires_at": "2026-04-08T00:00:00Z"}Token properties
Section titled “Token properties”- Re-usable: Tokens can be used multiple times before expiry. Users can re-record.
- Scoped: Each token is tied to a specific collection + user pair.
- Default TTL: 7 days. Extend up to 30 days with
expires_in. - Prefix: All tokens start with
emb_tk_for easy identification.
Token lifecycle
Section titled “Token lifecycle”Generate token → User opens recorder → Records name → Token remains valid ↓ Can re-record until token expiresSecurity considerations
Section titled “Security considerations”- Embed tokens grant recording permission for one specific user — they cannot be used to access other users’ data
- Tokens do not expose your API key
- Expired tokens show a friendly error page to the user