Get users
Changed onRetrieve all users.
Top level filters use AND, while individual filters use OR if they accept multiple arguments. That means filters will be resolved like this: (id IN ids) AND (remote_id IN remote_ids)
Request
- Base URLhttps://api.kombo.dev/v1
- AuthHTTP bearer
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Query parameters
An optional cursor string used for pagination. This can be retrieved from the next property of the previous page response.
The number of results to return per page. Maximum is 250.
Filter the entries based on the modification date in format YYYY-MM-DDTHH:mm:ss.sssZ. Returns records where either the record itself OR its nested data has been updated since this timestamp, even if the record's own changed_at field remains unchanged.
If you want to track entry deletion, also set the include_deleted=true query parameter, because otherwise, deleted entries will be hidden.
For more details, see Understanding changed_at vs updated_after Behavior.
For this endpoint, updated_after matches when the returned record changed, or when related data changed as described below.
| Path | Added/Removed | Linked Record |
|---|---|---|
| system_role_assignment | ✓ Yes | ✓ Yes |
Added/Removed: Whether adding or removing entries from this list triggers an update (n/a for single records). Linked Record: Whether changes to the linked record itself trigger an update.
By default, deleted entries are not returned. Use the include_deleted query param to include deleted entries too.
When set to true, filters targeting fields not supported by this integration will be ignored instead of filtering out all results.
Filter by a comma-separated list of IDs such as 222k7eCGyUdgt2JWZDNnkDs3,B5DVmypWENfU6eMe6gYDyJG3.
Filter by a comma-separated list of remote IDs.
Filter by a comma-separated list of emails. We will only return users who have any of the emails. The format of the emails is case-insensitive.
Headers
ID of the integration you want to interact with.
Response
GET /ats/users Positive response
Example response
{
"data": {
"next": "eyJwYWdlIjoxMiwibm90ZSI6InRoaXMgaXMganVzdCBhbiBleGFtcGxlIGFuZCBub3QgcmVwcmVzZW50YXRpdmUgZm9yIGEgcmVhbCBjdXJzb3IhIn0=",
"results": [
{
"id": "26vafvWSRmbhNcxJYqjCzuJg",
"remote_id": "32",
"first_name": "John",
"last_name": "Doe",
"email": "john.doe@kombo.dev",
"status": "ACTIVE",
"remote_data": null,
"changed_at": "2022-08-07T14:01:29.196Z",
"remote_deleted_at": null,
"system_roles": [
{
"remote_id": "1",
"remote_label": "Admin",
"unified_type": "ADMIN",
"scope": "SYSTEM"
}
]
}
]
}
}Changes
- breaking
the response property
///became optional for the status - breaking
the
///response's property type changed fromstringtostringnull, and format fromemailto no format for status - info
added the new optional
queryrequest parameteremails - info
added the new optional
queryrequest parameterignore_unsupported_filters - info
removed the pattern
/^([\da-z]{24}(,[\da-z]{24})*)?$/ifrom thequeryrequest parameterids - info
removed the non-success response with the status
- info
removed the non-success response with the status
- info
removed the non-success response with the status
- info
removed the non-success response with the status
- info
removed the non-success response with the status
- info
the
response property const valuesuccesswas added for the status - info
removed the
successenum value from theresponse property for the response status - info
the
///response's property pattern^(?!\.)(?!.*\.\.)([\w'+-.]*)[\w+-]@([\da-z][\da-z-]*\.)+[a-z]{2,}$was added for the status - info
added the required property
///to the response with the status - info
added the required property
///to the response with the status
- breaking