v1

latestOpenAPI 3.0.12026-08-0621301.7 MB
Leads

Get all archived leads

Returns multiple archived leads. Leads are sorted by the time they were created, from oldest to newest. Pagination can be controlled using limit and start query parameters. If a lead contains custom fields, the fields' values will be included in the response in the same format as with the Deals endpoints. If a custom field's value hasn't been set for the lead, it won't appear in the response. Please note that leads do not have a separate set of custom fields, instead they inherit the custom fields' structure from deals.

get/leads/archived

Query parameters

limitinteger
Example:100

For pagination, the limit of entries to be returned. If not provided, 100 items will be returned.

startinteger

For pagination, the position that represents the first result for the page

owner_idinteger
Example:1

If supplied, only leads matching the given user will be returned. However, filter_id takes precedence over owner_id when supplied.

person_idinteger
Example:1

If supplied, only leads matching the given person will be returned. However, filter_id takes precedence over person_id when supplied.

organization_idinteger
Example:1

If supplied, only leads matching the given organization will be returned. However, filter_id takes precedence over organization_id when supplied.

filter_idinteger
Example:1

The ID of the filter to use

sort'id' | 'title' | 'owner_id' | 'creator_id' | 'was_seen' | 'expected_close_date' | 'next_activity_id' | 'add_time' | 'update_time'

The field names and sorting mode separated by a comma (field_name_1 ASC, field_name_2 DESC). Only first-level field keys are supported (no nested keys).

Response

Successful response containing payload in the data field

successboolean