Personal Access Tokens
Personal Access Tokens (PAT) are personal authentication tokens that let you access Recrut'Auto from your external tools: MCP server, REST API, scripts, in-house integrations. They are scoped to your subscription and respect your permissions.
Generate a token
- Log in to console.recrutauto.fr.
- Open your user menu (top right) then click My account.
- Scroll down to the Access tokens section.
- Enter a descriptive name (e.g. "Claude Desktop — my Mac", "ATS sync script", "Cursor desktop").
- Click Create token.
The token then appears in clear text, prefixed with ra_:
ra_a1b2c3d4e5f6...
The full token is displayed only once, at creation time. Copy it immediately and store it in a secrets manager (1Password, Bitwarden, a .env.local environment variable, etc.). If you lose it, revoke it and generate a new one.
Token list
For each token, the section shows:
| Field | Description |
|---|---|
| Name | The name you chose |
| Prefix | The first 8 characters (e.g. ra_a1b2c3...), for identification only |
| Created on | Creation date |
| Last used | Timestamp of the last authenticated call with this token |
| Expires on | Expiration date if configured (optional) |
| Status | Active / Inactive |
Revoke a token
- In the list, click the trash icon to the right of the token.
- Confirm the revocation.
The token is invalidated immediately: any request using it will receive a 401 Unauthorized error. This action is irreversible.
- One token per integration — easier to revoke individually if compromised.
- Explicit naming — include the machine or tool (e.g. "Work laptop — Cursor").
- Watch "Last used" — revoke dormant tokens.
- Never commit a token to Git — always use an environment variable.
Personal tokens vs organization keys
Recrut'Auto distinguishes two kinds of tokens:
| Personal Access Token | Organization API key | |
|---|---|---|
| Where to create | My account › Access tokens | Organization › Developers |
| Prefix | ra_… | ra_live_… / ra_test_… |
| Scope | You (your campaigns, candidates, permissions) | The organization (CI/CD, server integrations) |
| MCP server (Claude) | ✅ Yes | ❌ No |
| REST API | ✅ Yes | ✅ Yes |
To use Claude (MCP server), create a personal token: the MCP server always acts as an identified member and does not accept organization keys. Organization keys are for server-to-server integrations (CI/CD, ATS sync, SCIM) on the REST API, and are managed under Organization › Developers.
Usage
Once your token is generated, see:
- MCP documentation — to configure Claude Desktop, Cursor, or Claude Code.
- REST API — to call the HTTP endpoints directly.