Authentication options
Never store credentials in plaintext.
Authentication through JWT
You will need to authenticate when interacting with our API. All Open API requests uses Bearer authentication with JSON Web Tokens (see RFC 7519).
The client must set the Authorization header to 'Bearer \'.
The token is personal and unique for each user and a specific domain, as indicated on creation. Tokens can be created in the Flow Web Application in Settings - My Account - Username and password.
Authentication through Basic Authentication
We recommend JWT tokens for authentication, however we also support BasicAuth. See RFC 7617. When an administrator or third party application needs your Flow credentials, providing a JWT can be used as a safer alternative.
See below for an example.
Authentication through JWT
You will need to authenticate when interacting with our API. All Open API requests uses Bearer authentication with JSON Web Tokens (see RFC 7519).
The client must set the Authorization header to 'Bearer \
The token is personal and unique for each user and a specific domain, as indicated on creation. Tokens can be created in the Flow Web Application in Settings - My Account - Username and password.
Authentication through Basic Authentication
We recommend JWT tokens for authentication, however we also support BasicAuth. See RFC 7617. When an administrator or third party application needs your Flow credentials, providing a JWT can be used as a safer alternative.
See below for an example.
- A request to this endpoint with the HTTP header 'Authorization: Bearer
' will authenticate the request to '/calls' for the user. - A request to "/auth/login" with the HTTP header 'Authorization: Basic MDEyMzQ1Njc4OnZlcnlzZWNyZXQ=' will make the user with the username "012345678" and the password "verysecret" login, and return a cookie for future Authentication.