List IntelliAppZ
Overview
List IntelliAppZ associated with the authenticated Implementation Partner.
Endpoint
GET /api/integration/partner/appz/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
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/appz/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.
{
"partner": {
"partnerId": 1,
"firstName": "Alex",
"lastName": "Example",
"emailAddress": "partner@example.com",
"phone": "+1-202-555-0100",
"jobTitle": "CEO",
"companyName": "Pym Technologies",
"country": "United States",
"city": "California",
"industry": "Pharma",
"businessRegion": "North America;#South America;#Western America;#Eastern America",
"partnerType": "Implementation Partner",
"status": "Active",
"number": "IBPR20241217000001",
"state": null,
"postalCode": null,
"address": null,
"created": "2024-12-17T02:13:18.868908",
"modified": "2024-12-17T02:14:29.522617",
"createdBy": "Sample User",
"modifiedBy": "Sample User"
},
"intelliAppZ": [
{
"intelliAppzId": 8,
"name": "Sample",
"id": "4B7CA9E3-C87E-4B49-ABD7-52AF75AF1AF5",
"version": "1.0.1",
"unitType": "page",
"description": "for testing",
"reviewerComment": "",
"status": "New",
"isHavingSubscription": false,
"creditMappings": [],
"created": "2025-04-22T06:00:02.686296",
"modified": "2025-04-22T06:00:02.686296",
"createdBy": "Sample User",
"modifiedBy": "Sample User"
}
]
}
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 |
|---|---|---|
partner | object | Profile of the authenticated partner. |
intelliAppZ | array | IntelliAppZ configurations matching the request. |
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 IntelliAppZ access or is not authenticated as a partner. |
| 404 | Not Found – No partner record is associated with the authenticated user. |
| 500 | Internal Server Error – An unexpected error occurred during request processing. |