👍
If no offline token has been previously created for the end-user, a new one will be issued in the response of this endpoint.

📘
Storing the offline_token
Storing the offline_token for your end-users enables you to implement the Frictionless Sign-up/Sign-in flow and improve user experience.

Authentication

To authenticate this request, generate the JWT Token by following the instructions on Frictionless Sign-up flow setup page, excluding Step 3 of the instructions.

The JWT payload must contain the email equal to the email in this request body.

👍
The JWT token should be sent as a Bearer token in the Authorization header as shown in the request below.

If no offline token has been previously created for the end-user, a new one will be issued in the response of this endpoint.

Storing the `offline_token`

Authentication

The JWT token should be sent as a `Bearer` token in the `Authorization` header as shown in the request below.

If no offline token has been previously created for the end-user, a new one will be issued in the response of this endpoint.

Storing the offline_token

Authentication

The JWT token should be sent as a Bearer token in the Authorization header as shown in the request below.

Storing the `offline_token`

The JWT token should be sent as a `Bearer` token in the `Authorization` header as shown in the request below.

200200

400400