Welcome to the new Daily Docs. Please let us know what you think.

Self-signing tokens

If you're unfamiliar with JWTs and how to create them, please use the existing /meeting-tokens endpoints

Generating self-signed tokens

Using your API key, you can self-sign tokens that will be accepted by the backend, as long as the API key is still active at the time it is checked. This saves making a round-trip to the Daily API to generate tokens, which is great if you need to update the tokens often or create them in bulk.

You can create a JWT using your domain's API key as the secret and making the payload include a room name ("r"), the current time ("iat"), and the domain_id ("d") like:

{ "r": "test", "iat": 1610596413, "d": "30f866c3-9123-452a-8723-ff58322d09c5"}

Note: The domain_id is available from the domain configuration endpoint.

To learn more about, and test, your tokens please refer to https://jwt.io/.

Configuration properties in tokens use the following abbreviations:

Propertyabbreviated
nbfnbf
expexp
domain_idd
room_namer
user_idud
user_nameu
is_ownero
close_tab_on_exitctoe
redirect_on_meeting_exitrome
intercom_join_alertij
start_cloud_recordingsr
enable_recordinger
enable_screensharess
start_video_offvo
start_audio_offao
meeting_join_hookmjh
eject_at_token_expejt
eject_after_elapsedeje
languil