Skip to main content
The FlowForma Governance API accepts two kinds of credential. Which one you use depends on the endpoint.

Azure AD bearer token

Used by most endpoints (environments, environment requests, processes, security templates, settings). Obtained from an Azure AD app registration.

Integration access token

Required by the Process Actions and API Connections endpoints. Copied from FlowForma Settings.
All requests are made against the base URL https://api.flowforma.com.

Azure AD bearer token

Most endpoints authenticate with an Azure AD app-only access token.
1

Register an Azure AD app

Create an app registration with the Sites.Read.All Microsoft Graph application permission and a client secret. Follow the App Registration guide. Note the Application (client) ID, Directory (tenant) ID, and client secret.
2

Request a token

Call the token endpoint with those three values as query parameters:
The response body is the access token.
3

Call the API

Send the token in the Authorization header using the Bearer scheme:
The API resolves your tenant from the token, so no tenant identifier is needed on individual calls.

Integration access token

The Process Actions and API Connections endpoints require a FlowForma integration access token instead of a bearer token. If you send a bearer token to these endpoints, the request is rejected.
1

Copy the token

In your FlowForma environment, open FlowForma Settings and copy the integration access token.
2

Call the API

Send the token as the raw Authorization header value, with no Bearer prefix:
The integration access token is sent without the Bearer prefix. The Azure AD token is sent with it. Using the wrong one for an endpoint results in an error.