Sign in with OAuth 2.0 (client credentials)
Applications that talk to each other often sign in with OAuth 2.0 client credentials: with a client_id and client_secret they fetch a short-lived token (one hour) from the token endpoint, and send it along as a bearer token. Flow's gateway is that token issuer itself. You create a policy with OAuth 2.0 and a required permission, a client with that permission, fetch a token and call the API with it.
A policy with OAuth 2.0 and a required permission
Under Security you create a policy: API key off, OAuth 2.0 on, and under Required scopes the permission every consumer must have.
Create an OAuth client
Under Security → OAuth clients you give the application a name and the permissions it gets. You see once the client_id, the client_secret and the address of the token endpoint: hand them to the application's administrator.
Call the API with the token
The application sends grant_type=client_credentials with its client_id and client_secret to the token endpoint and gets a token that is valid for one hour. That token goes along as a Bearer token. In Test APIs you do the same: choose Bearer token and paste the token.
This guide was carried out step by step on 22 Oct 2026 by an automated test on Flow (version 3e563176).






























