Skip to main content
The DeepCurrent API supports two authentication methods. Both produce a Bearer token you pass in the Authorization header on every request. 
Authorization: Bearer <token>

​
Method 1 — API key

API keys are the recommended method for programmatic access. Keys are prefixed with dc_ and do not expire. You can generate or reveal your API key from the DeepCurrent dashboard or via GET /api/v1/users/me/api-key?reveal=true. 
curl https://api.deepcurrent.app/api/v1/users/me \
  -H "Authorization: Bearer dc_your_api_key_here"
API keys are shown only once at generation time. Store the key securely — if you lose it you must request a regeneration via POST /api/v1/users/me/api-key/regenerate-request.

​
Method 2 — JWT (email + password)

Exchange your email and password for a short-lived JWT access token. This is suitable for interactive sessions and testing.

​
Endpoint

POST /api/v1/login/access-token

​
Request

Send as application/x-www-form-urlencoded:
​
username
string
required
Your account email address.
​
password
string
required
Your account password.

​
Response

​
access_token
string
The JWT token to use as a Bearer credential.
​
token_type
string
Always "bearer".

​
Example

curl -X POST https://api.deepcurrent.app/api/v1/login/access-token \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "username=you@example.com&password=yourpassword"
Response
{
  "access_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
  "token_type": "bearer"
}
Use the returned access_token as your Bearer token on subsequent requests: 
curl https://api.deepcurrent.app/api/v1/users/me \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."