Skip to main content
curl --request POST \
  --url https://${projectDomain}/v1/oauth2/token \
  -H 'Content-Type: application/json' \
  -d '{
    "client_id": "connected-app-test-d731954d-dab3-4a2b-bdee-07f3ad1be888",
    "client_secret": "NHQhc7ZqsXJVtgmN2MXr1etqsQrGAwJ-iBWNLKY7DzJq",
    "grant_type": "refresh_token",
    "refresh_token": "PvC5UudZ7TPZbELt95yXAQ-8MeEUCRob8bUQ-g52fIJs"
  }'

{
  "access_token": "eyJ...",
  "expires_in": 3600,
  "refresh_token": "wUU...",
  "scope": "openid email profile phone",
  "token_type": "bearer",
  "id_token": "eyJ...",
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "status_code": 200
}
POST
https://${projectdomain}
/
v1
/
oauth2
/
token
curl --request POST \
  --url https://${projectDomain}/v1/oauth2/token \
  -H 'Content-Type: application/json' \
  -d '{
    "client_id": "connected-app-test-d731954d-dab3-4a2b-bdee-07f3ad1be888",
    "client_secret": "NHQhc7ZqsXJVtgmN2MXr1etqsQrGAwJ-iBWNLKY7DzJq",
    "grant_type": "refresh_token",
    "refresh_token": "PvC5UudZ7TPZbELt95yXAQ-8MeEUCRob8bUQ-g52fIJs"
  }'

{
  "access_token": "eyJ...",
  "expires_in": 3600,
  "refresh_token": "wUU...",
  "scope": "openid email profile phone",
  "token_type": "bearer",
  "id_token": "eyJ...",
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "status_code": 200
}
This endpoint uses your Custom Domain. The refresh_token grant type is used to periodically exchange a refresh token for a new access token without user interaction. When using the refresh_token grant type, a refresh_token must be provided. This endpoint returns different responses depending on the client being used:
  • If a First Party Public or Third Party Public client is used, the original refresh token sent in the request will be rotated out and a new refresh_token will be present in the response. You must save this new token for next time. Each refresh token has an expiry of 3 months from issuance.
  • If a First Party Confidential or Third Party Confidential client is used, no token rotation will occur. The refresh token used in the request will remain valid for future use and no new refresh_token will be present in the response. The refresh token has an initial expiry of 3 months, and each use extends its lifetime by another 3 months.
Connected App Access Tokens are JWTs signed with the project’s JWKS. Access Tokens expiry is controlled by the client’s access_token_expiry_minutes field, which defaults to one hour. You can validate and examine your access and refresh tokens by using the Token Introspection Endpoint. Access token JWTs can be validated locally by using a Stytch Backend SDK, or any library that supports the JWT protocol.
Unlike other Stytch API endpoints, this endpoint is not authenticated with a project_id and project_secret pair. Instead, it is authenticated via the client_id and client_secret of an active Connected App Client within the current project.
This endpoint is an RFC-6749 compliant token issuing endpoint.
  • This endpoint supports passing the client_id and client_secret within the request body as well as within a HTTP-Basic Auth header.
  • This endpoint supports both application/json and application/x-www-form-urlencoded content types.
We recommend using the Custom Domain whenever possible. For backwards compatibility reasons, this endpoint is also available at https://test.stytch.com/v1/public/${projectId}/oauth2/token.

Body

client_id
string
required
The ID of the Connected App client.
client_secret
string
required
The secret of the Connected App client. Required for confidential clients
grant_type
string
required
The OAuth2 defined grant type that should be used to acquire an access token. Either authorization_code or refresh_token is supported for Connected App clients. An error will be returned if this parameter is omitted.
refresh_token
string
required
A refresh token previously issued to the client. This field is required when using the refresh_token grant.

Response

access_token
string
The access token granted to the client. Access tokens are JWTs signed with the project’s JWKS.
refresh_token
string
An opaque token that may be used in the future to retrieve a new access token. Only returned if the offline_access scope is granted.
token_type
string
The type of the returned access token. Today, this value will always be equal to “bearer”
expires_in
number
The lifetime in seconds of the access token. For example, the value 3600 denotes that the access token will expire in one hour from the time the response was generated.