limit and cursor parameters.
Filters by endpoint
List credentials
List credentials
GET /v2/credentialsReturn only credentials for a specific source.
Filter by credential status. One of
unverified, verified, invalid, deleted.Filter by the external ID you assigned when creating the credential. Useful for finding all credentials belonging to a specific user in your system.
List tasks
List tasks
List task runs
List task runs
GET /v2/task-runsFilter by agent.
Filter by credential. Returns only runs that used a specific credential.
Filter by source.
Filter by task.
Filter by run status. One of
queued, running, cancelling, interaction_required, review_required, completed, canceled, failed.Filter by run result. One of
success, failure, unknown. Maps to the result field on the task run object.Return runs created after this timestamp (ISO 8601).
Return runs created before this timestamp (ISO 8601).
List event destinations
List event destinations
GET /v2/event-destinationsFilter by destination status. One of
pending_verification, active, inactive.List deliveries for a destination
List deliveries for a destination
GET /v2/event-destinations/{destination_id}/event-deliveriesFilter by delivery status. One of
success, failure.List events
List events
Endpoints without filters
The following list endpoints only support pagination (limit and cursor) with no additional filters:
GET /v2/agentsGET /v2/sources
Combining filters with date ranges
For endpoints that supportcreated_after and created_before, you can combine them to query a specific window of time.
Tips
- Filter server-side. Fetching all records and filtering in your app wastes bandwidth and API quota.
- Combine filters. All query parameters are AND-combined, so adding more filters narrows results.
- Use date ranges for historical queries.
created_afterandcreated_beforeare the most efficient way to pull data for a time window. - Pair with pagination. Large result sets should use
limitandcursortogether with filters. See the pagination guide for details.
Pagination
Navigate large result sets with cursor-based pagination.
Using the API
Authentication, base URLs, and request conventions.