Skip to main content
Use this flow when your own backend calls the API using your own account. There is no user to prompt, so there is no consent screen and no redirect. It requires a Service application.

How it works

Your server sends its client_id and client_secret to the token endpoint and receives an access token. The token acts as the account that owns the application.
With this flow, GET /api/v1/user returns the profile of the account that owns the application. Grant the profile:read scope to the application to use it.

Request a token

You can also send the credentials with HTTP Basic auth instead of the body.
A successful response returns an access token that lasts one hour. There is no refresh token. Request a new token when the current one is close to expiry.

Call the API

Send the token as a bearer token against the versioned REST API.

Use the SDK

The Nemu client handles the token for you. It fetches a token on the first call and caches it until it is close to expiry.
See the SDK guide for the full surface.
The client_secret grants full access to everything the application can do. Keep it on your server and rotate it from the console if it leaks.