Quick start
To get started with the Headless APIs, follow these steps.
Last updated
To get started with the Headless APIs, follow these steps.
Last updated
We use a token based authorization mechanism for both Member and Auth APIs.
Community admins can obtain an API key by going to the Developers -> Tokens page in their community and selecting the type as Headless Auth.
IMPORTANT: You will need to use the token type `Headless Auth` for it to work with the Auth APIs.
After generating your API token from the Developers tab, you'll need to fetch a signed in member's unique JWT token so you can make requests on their behalf with our . To authenticate a member and receive the JWT access token, you'll need to pass one of the following params:
community_member_id: the member's Circle community member ID
email: the member's email
sso_id: if you've setup SSO, this will likely be the user ID within your SSO auth system. For instance, a Google ID via Auth0 will look something like "google-oauth2|106228182038999999999"
This response includes:
access_token
: A JWT token used for authenticating subsequent API requests.
refresh_token
: A token used to obtain a new access token when the current one expires.
access_token_expires_at
: The expiration timestamp for the access token. It expires after 1h.
refresh_token_expires_at
: The expiration timestamp for the refresh token. It expires after 1 month.
community_member_id
: The ID of the community member associated with this token.
community_id
: The ID of the community the member belongs to.
Once you've retreived the member's access_token,
you can make requests on their behalf to the Headless Member API. For example:
For a full list of member API endpoints, .
To reach out to our API engineering team with feedback or requests, .