List Subscriptions
Overview
List subscriptions associated with the authenticated Implementation Partner. Optionally filter by customer ID.
Endpoint
GET /api/integration/partner/subscription/all
Use the service origin described in Getting started. The path above already includes /api.
Authentication
Send the access token obtained from Get Access Token in the Authorization header. Access is limited by the authenticated account’s permissions.
Request headers
Accept: application/json
Authorization: Bearer ACCESS_TOKEN
Query parameters
| Parameter | Type | Requirement | Description |
|---|---|---|---|
customerId | integer | Optional | Customer ID associated with the authenticated partner. |
Request example
The following example uses cURL in a POSIX shell. Replace example credentials and IDs before running it.
curl --request GET \
--url 'https://accounts.onintellibuddies.com/api/integration/partner/subscription/all' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer ACCESS_TOKEN'
Response
Successful status: 200 OK.
The following is an illustrative response with synthetic contact and credential values. Arrays are shortened to one representative item.
[
{
"id": 29,
"subscriptionNumber": "IBIS20250131000029",
"description": "Test-subscription-for-auto-renewal - Production",
"licenseType": "PRODUCTION",
"approvalDays": 3,
"expiresOn": "2025-02-03T23:59:59",
"activatedOn": "2025-01-31T12:47:56.368987",
"skuCode": "400010",
"partnerId": 1,
"customerId": 1,
"neverExpires": false,
"autoRenewal": false,
"type": "New",
"edition": "INTELLIAPPZ",
"status": "Expired",
"created": "2025-01-31T12:45:45.14649",
"modified": "2025-01-31T12:46:02.153696",
"createdBy": "Sample User",
"modifiedBy": "Sample User"
}
]
Response fields
The response is an array. The table describes fields in an item. Types reflect the example; this is not an exhaustive schema or nullability contract.
| Field | Example type | Description |
|---|---|---|
subscriptionNumber | string | Public subscription number. |
partnerId | integer | ID of the partner. |
status | string | Resource or operation status shown in the example; the complete allowed set is not defined here. |
Errors
Documented error statuses are listed below. Exact response bodies and validation details are not documented.
| Status | Description |
|---|---|
| 400 | Bad Request – The partner ID or user ID is invalid. |
| 401 | Unauthorized – Authentication is required to access this resource. |
| 403 | Forbidden – The user lacks subscription access or is not authenticated as a partner. |
| 404 | Not Found – No partner is associated with the authenticated user. |
| 500 | Internal Server Error – An unexpected error occurred during request processing. |