Doppler token
ID doppler_token
DatatypeNot PIIidentifierDraft
This record is a draft: it has not been reviewed yet and may be incomplete or wrong. Do not rely on it for compliance decisions. Help improve it (see CONTRIBUTING.md).
Access token of the Doppler secrets manager. Doppler documents one format per token type, each starting with dp. and a type code: dp.pt. (personal), dp.st. (service, optionally followed by a lowercase name of 2 to 35 characters and a dot), dp.ct. (CLI), dp.sa. (service account), dp.scim. (SCIM) and dp.audit. (audit). 40 to 44 letters and digits follow.
- Parent datatype
- Access token
access_token - Categories
- Secrets and credentials (passwords, keys, tokens)
- Countries
- Global (not tied to a country)
- Languages
- Common to most languages
- Quality
- 70/100 · missing: examples, mapping (Wikidata, Schema.org, ...), translation
- Metacrafter rules
- no detection rule yet
- Supported by tools
- Gitleaks, TruffleHog
Regular expression
^dp\.(?:(?:pt|ct|sa|scim|audit)\.|st\.(?:[a-z0-9_-]{2,35}\.)?)[A-Za-z0-9]{40,44}$
Python re syntax.
Examples
| Value | Description |
|---|---|
| dp.pt.ExampleTokenNotReal invalid | Too short |
Sources
- doc: https://docs.doppler.com/reference/auth-token-formats
- other: https://github.com/gitleaks/gitleaks/blob/master/config/gitleaks.toml
- other: https://github.com/trufflesecurity/trufflehog/blob/main/pkg/detectors/doppler/doppler.go
Use this record
- Page URL:
http://registry.apicrafter.io/datatype/doppler_token - JSON: API v1 · legacy shape (used by metacrafter) · Markdown (for LLMs)
- Improve it: edit
data/datatypes/any/secrets/doppler_token.yamlon GitHub