Skip to main content
Dugble’s public API uses team tokens for authentication. Team tokens are scoped to a single team and carry an explicit set of permissions.

Bearer authentication

Send your team token in the Authorization header on every API request.
For example:
Team token secrets use the dgb_team_ prefix. Keep them server-side and never expose them in client-side code or public repositories.

Team scope

A team token is already bound to the team that created it. You do not need to send an X-Team-ID header when authenticating with a team token.

Permissions

Each token has one or more permissions. The Email and SMS API currently uses these permissions: Use the smallest permission set your integration needs.

Expiration and revocation

Team tokens can expire and can be revoked. Requests made with an invalid, expired, or revoked token return 401 UNAUTHORIZED. A valid token that does not have the permission required by an endpoint returns 403 FORBIDDEN.

Example request

See Idempotency for guidance on safely retrying mutation requests.