auth

Exchange Formify API key for short-lived access token

Exchange a Formify API key, for example sk_live_YOUR_API_KEY, for a short-lived Bearer access_token. Test keys use the same format with the sk_test_ prefix.

OAuth 2.0 with PKCE remains the recommended authentication method for integrations that support it. This endpoint exists for MCP clients and third-party platforms that cannot complete OAuth/PKCE and only allow a user to paste a token.

Send the API key in the Authorization header using the ApiKey scheme:

Authorization: ApiKey sk_live_YOUR_API_KEY

The response contains an access_token that is used exactly like an OAuth access token:

Authorization: Bearer {access_token}

Do not call protected API endpoints directly with the API key.

post/auth/token

Request

Base URL: https://docs-api.formify.eu/v1
URL: https://docs-api.formify.eu/v1/auth/token
Auth: HTTP apikey

Query parameters

scope'read' | 'write' | 'read write'

Requested access scope. Use read, write, or read write. Defaults to read write if omitted.

Response

Access token generated successfully

access_tokenstring required

The short-lived JWT access token used for authenticating API requests.

expires_ininteger required

The lifetime of the access token in seconds.

token_typestring required

The type of token issued. Always Bearer.

scopestring required

Space-separated list of permissions granted to this token (read, write, or read write).

Example response

{
  "access_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
  "expires_in": 3600,
  "token_type": "Bearer",
  "scope": "read write"
}

Changes

No recorded changes to this operation across all 1 revision of this API.