Skip to content
Abi Global HealthAbi Global HealthAbi Docs

Authentication and sub-partners

Abi API requests use bearer access tokens generated from partner credentials. Authentication belongs in your server-side integration.

  1. Send the partner credentials to the token operation documented in the API reference.
  2. Store the returned access and refresh tokens in your server-side secret store.
  3. Send the access token in the Authorization: Bearer <token> header.
  4. Refresh the token before or after expiry using the documented refresh operation.

Sub-partner access

Section titled “Sub-partner access”

Where an integration operates multiple brands, services, or environments, Abi can scope a token using subPartnerName. When that scope is embedded in the token, requests should not duplicate the value in individual request bodies unless the API contract requires it.