Does my SSO user need a separate password to use the Allocadia API?

Yes. To use the API, a user needs API access enabled plus a password — separate from SSO. Most teams use a dedicated integration user.

Yes. In Allocadia, regular users without API access enabled can only log in via SSO — they don't have a local password and can't authenticate to the API.

To use the API, a user needs:

1. API access enabled on their user record. An admin grants this.
2. A local password set on their account. This password is used only for API authentication and is separate from their SSO login.

The typical pattern

Most customers create a dedicated integration user (e.g. customer.integrations@example.com) with API access enabled and a strong password. The credentials are stored securely on the integration side and used to obtain tokens against the Allocadia REST API.

Regular human users continue to log in via SSO; only the integration user authenticates with a password.

How to set this up

Contact Support — we can enable API access on a user and provide the password to the team responsible for the integration.

Related articles

• REST API authentication in Allocadia (bearer token, 20-minute timeout)
• SSO setup — Microsoft Entra ID with Allocadia
• SSO setup — Okta with Allocadia
• The Allocadia REST API — overview of endpoints