---
id: "typeform_personal_access_token"
kind: "datatype"
status: "draft"
is_pii: false
categories: ["secrets"]
langs: ["common"]
quality: 70
url: "https://registry.apicrafter.io/datatype/typeform_personal_access_token"
---

# Typeform personal access token (`typeform_personal_access_token`)

> **Draft.** Draft records have not been reviewed yet and may be incomplete or wrong; do not treat them as authoritative for legal or compliance decisions.

Personal access token of the Typeform API. The Typeform documentation shows a sample token that starts with tfp_ followed by 40 hexadecimal digits, while gitleaks expects 59 characters after the prefix; the regexp accepts 40 to 59 letters, digits and the characters _ . = -.

- Parent datatype: `access_token`
- Personal data (PII): no
- Categories: Secrets and credentials (passwords, keys, tokens) (secrets)
- Countries: global
- Languages: Common to most languages (common)
- Classification: identifier

## Detection

Regular expression (Python `re`):

```
^tfp_[A-Za-z0-9_.=-]{40,59}$
```

## Examples

- `tfp_` (invalid example) — Prefix without the secret

## Supported by tools

- `datadogsds`
- `gitguardian`
- `githubsecretscanning`
- `gitleaks`

## Sources

- doc: <https://www.typeform.com/developers/get-started/personal-access-token/>
- other: <https://github.com/gitleaks/gitleaks/blob/master/config/gitleaks.toml>

## Quality

Score 70/100. Missing: examples, mapping (Wikidata, Schema.org, ...), translation.

JSON: <https://registry.apicrafter.io/api/v1/datatypes/typeform_personal_access_token.json> · Edit: <https://github.com/apicrafter/metacrafter-registry/edit/main/data/datatypes/any/secrets/typeform_personal_access_token.yaml>