Authentication
Pulsus API
The Pulsus API uses OAuth 2.0 Client Credentials. Each integration receives a
client_id and client_secret, which are used to obtain a temporary access
token. Send the access token as a Bearer token with each API request.
Evolving authentication for integrations
Static API tokens have traditionally provided a simple way to authenticate integrations and continue to be used across many APIs.
As API platforms have evolved, OAuth 2.0 has become one of the most widely adopted industry standards for authentication and authorization. The Client Credentials flow is specifically designed for machine-to-machine and server-to-server integrations and is supported across modern identity and API platforms.
As part of the evolution of the Pulsus Public API, new APIs use OAuth 2.0 Client Credentials. This approach aligns the platform with modern security practices and provides a stronger foundation for managing integration identities, access permissions, credential lifecycle, and future API capabilities.
Each integration receives a client_id and client_secret, which are used to obtain a temporary access token. The access token can be reused while it remains valid — it does not need to be generated for every API call. When it expires, the integration can request a new token using the same credentials.
OAuth 2.0 is an IETF standard. The Client Credentials grant is defined in RFC 6749.
Legacy API
The Legacy API uses an API token provided by Pulsus. Send this token with each
request in the ApiToken HTTP header.
Getting credentials
Credentials for both the Pulsus API and the Legacy API are currently provided by Pulsus Support. Contact your Pulsus support channel to request access for your integration.
Use the credentials provided for the Pulsus portal you are accessing. Credentials issued for another portal are not interchangeable.
Get an access token
Use your client_id and client_secret to obtain a temporary access token.
You can generate it directly in this portal or request it from your
integration.
Generate in this portal
cURL example
curl --request POST \
"https://eu.auth.pulsus.mobi/realms/pulsus-public-europe/protocol/openid-connect/token" \
--header "Content-Type: application/x-www-form-urlencoded" \
--data-urlencode "grant_type=client_credentials" \
--data-urlencode "client_id=YOUR_CLIENT_ID" \
--data-urlencode "client_secret=YOUR_CLIENT_SECRET"
The response includes an access_token and expires_in. Reuse the access token while it remains valid. When it expires, request a new one using the same client_id and client_secret.
Store your client_secret securely and never expose it in client-side
applications.
Access scope
Each integration is authorized for a specific Pulsus account. The access token determines which resources and operations the integration can access.
Access may be read-only or include supported write operations, depending on the permissions assigned to the integration. Requests outside the authorized scope are rejected.
Troubleshooting
- 401 Unauthorized — The access token is missing, invalid, or expired. Authenticate again and retry.
- 403 Forbidden — The integration does not have permission to perform the requested operation.
- Authentication failed — Verify your
client_idandclient_secretand make sure they were issued for the Pulsus portal you are using. - Network error — If the authentication service cannot be reached from the portal, contact Pulsus Support.