GET /api/v2/users
Pagination
- Cursor pagination (recommended)
- Offset pagination
See Pagination.
Returns a maximum of 100 records per page.
Allowed For
- Admins, Agents and Light Agents
Servers
- https://{subdomain}.{domain}.com
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
page |
No |
Pagination parameter. Supports both traditional offset and cursor-based pagination:
These are mutually exclusive - use one format or the other, not both. |
|
external_id |
String | No |
List users by external id. External id has to be unique for each user under the same account. |
include_boundary_indicators |
Boolean | No |
When true, includes Only valid with cursor pagination (page[size], page[after], page[before]). |
include |
String | No |
Sideloads to include in the response. Accepts a comma-separated list of values. See Sideloading. |
per_page |
Integer | No |
Number of records to return per page. Note: Default and maximum values vary by endpoint. Check endpoint-specific documentation for limits. |
sort |
String | No |
Field to sort results by. Prefix with When used with cursor pagination, this determines the cursor ordering. Example: |
role[] |
String | No |
Filters the results by more than one role using the format |
permission_set |
Integer | No |
For custom roles which is available on the Enterprise plan and above. You can only filter by one role ID per request |
include_item_cursors |
Boolean | No |
When true, includes cursor values for each item in the cursor pagination response. Only valid with cursor pagination (page[size], page[after], page[before]). |
role |
String | No |
Filters the results by role. Possible values are "end-user", "agent", or "admin" Valid values:
|
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.