Get Access Token
Overview
Obtain an access token by signing in with your account credentials.
Endpoint
POST /api/integration/partner/login
Use the service origin described in Getting started. The path above already includes /api.
Authentication
This operation uses the credentials or refresh token in the request body.
Request headers
Accept: application/json
Content-Type: application/json
Request body
| Parameter | Type | Requirement | Description |
|---|---|---|---|
emailAddress | string | Required | Email address associated with the account. |
password | string | Required | Account password. |
{
"emailAddress": "partner@example.com",
"password": "REDACTED"
}
Request example
The following example uses cURL in a POSIX shell. Replace example credentials and IDs before running it.
curl --request POST \
--url 'https://accounts.onintellibuddies.com/api/integration/partner/login' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--data '{
"emailAddress": "partner@example.com",
"password": "REDACTED"
}'
Response
Successful status: 200 OK.
The following is an illustrative response with synthetic contact and credential values. Arrays are shortened to one representative item.
{
"access_token": "EXAMPLE_ACCESS_TOKEN",
"refresh_token": "EXAMPLE_REFRESH_TOKEN",
"expires_in": 1800,
"token_type": "Bearer"
}
Use access_token as the Bearer token. expires_in is the access-token lifetime in seconds; the example shows 1800 seconds. Store the returned refresh_token for the next refresh request. Refresh-token lifetime, rotation, and reuse rules require verification for your deployment.
Response fields
The table describes selected fields in the response. Types reflect the example; this is not an exhaustive schema or nullability contract.
| Field | Example type | Description |
|---|---|---|
access_token | string | Access token to send in the Bearer authorization header. |
refresh_token | string | Token used to obtain new access tokens. |
expires_in | integer | Access-token lifetime in seconds. |
token_type | string | Authorization scheme; the example uses Bearer. |
Errors
Documented error statuses are listed below. Exact response bodies and validation details are not documented.
| Status | Description |
|---|---|
| 400 | Bad Request — Invalid input or bad request. |
| 401 | Unauthorized – Invalid credentials. |
| 403 | Forbidden – User lacks necessary permissions. |
| 429 | Too Many Requests – Too many requests - Rate limit exceeded. |
| 500 | Internal Server Error – An unexpected error occurred during request processing. |