Framme

Client credentials

Your client_id and client_secret are issued by Framme, one pair per environment. Exchange them for an access token, then reuse that token until it expires.

Request a token

curl -X POST https://api.development.platform.framme.com/public/v1/oauth/token \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "grant_type=client_credentials" \
  -d "client_id=$FRAMME_CLIENT_ID" \
  -d "client_secret=$FRAMME_CLIENT_SECRET"

The response contains the token and its lifetime:

{
  "access_token": "…",
  "token_type": "Bearer",
  "expires_in": 3600
}

Use the token

curl https://api.development.platform.framme.com/public/v1/me \
  -H "Authorization: Bearer $ACCESS_TOKEN"

Caching, expiry & rotation

Cache the token and reuse it until expires_in elapses; request a new one when a call returns 401. To rotate or revoke a credential pair, contact your Framme representative — old tokens stop working once the pair is revoked.

Store credentials in environment variables or a secrets manager, never in client-side code or version control.