Build with the REST API

This quickstart takes you from partner credentials to an authenticated request. At the end, you will have an access token ready for user, subscription, consultation, and other API operations.

Prerequisites

• An Abi partner account.
• The credentials and environment details supplied by Abi.
• A server-side application that can keep credentials secret.

Keep credentials on your server

Never expose partner credentials or access tokens in browser code, mobile bundles, public repositories, or support messages.

1. Choose your environment

   Europe
   Use the production base URL assigned to your European integration.
   Hong Kong
   Use the Hong Kong base URL supplied with your partner account.
   China
   Use the China base URL supplied with your partner account.

2. Request an access token

   Send your partner credentials to the authorization token endpoint described in the generated API reference. Access tokens are returned as bearer tokens.

3. Send the token with API requests

   Send the bearer token in the Authorization header. Use one of the examples below as a starting point.

4. Handle token expiry

   Store tokens securely and refresh them through the documented refresh flow. Do not wait for repeated unauthorized responses before refreshing.

Request examples

cURL

curl --request GET \
  --url "${ABI_API_BASE_URL}/user/{id}" \
  --header "Authorization: Bearer ${ACCESS_TOKEN}"

JavaScript

const response = await fetch(`${ABI_API_BASE_URL}/user/${userId}`, {
  headers: { Authorization: `Bearer ${accessToken}` }
})

Next step

Continue with authentication and sub-partner access or browse the API reference.