Digital Samba Embedded
  • Getting started
    • Sign up to create a new team
    • Choose your subdomain
    • Authenticate to the API
    • Regenerate your developer key
  • Setting up your team
    • Update your subdomain
    • Customise your domain
    • Customize Access to Recordings, Transcripts, and Files
    • Add members to your team
    • Assign a team-role to your team members
    • Remove members
  • Configuring your room defaults
    • General settings
    • Branding
    • Components
    • Content Library
    • Recordings
    • Chat
    • Captions
    • Polls
    • Q&A
    • Transcription
    • Join settings
  • Creating a room
    • General settings
    • Branding
    • Components
    • Content Library
    • Recordings
    • Chat
    • Breakout rooms
    • Polls
    • Captions
    • Q&A
    • Transcription
    • Join settings
    • Telephony
    • External stream
  • Managing rooms
  • Adding moderation to your rooms with roles
    • Add roles to a room
    • Create a custom role
    • Permissions
  • Managing roles
  • Controlling room entry
  • Libraries
  • Recordings
  • Webhooks
  • Tokens
  • Troubleshooting sessions
    • Session details
    • Participant details
    • Participant log
  • Retrieving session data and reports
  • Understanding usage data
  • System check
  • REST API docs
  • SDK docs
  • LTI docs
Powered by GitBook
On this page
  1. Getting started

Authenticate to the API

Learn how to authenticate to our REST API with developer key and team id.

PreviousChoose your subdomainNextRegenerate your developer key

Last updated 1 year ago

When integrating Digital Samba Embedded you will most likely use the developer .

To make requests to it you need to authenticate with your developer key and team id. They can be found in the section after you sign up.

Include an Authorization http header with your team id and developer key separated by colon and then base64 encode the concatenated string. To make an analogy - you can think of team id as a username and developerKey as a password.

Both Bearer and Basic Authentication tokens are supported. Authorization: Bearer base64(teamId:developerKey) and Authorization: Basic base64(teamId:developerKey)

Never expose your developer key to the outside world or in frontend code. Its role is similar to a password, so protect it with care the same way you are protecting your passwords and other secrets. If you think your developer key has leaked or has been breached you can always regenerate it in our dashboard from the team section.

REST API
dashboard team
Team section in your dashboard including developer key and team id