/contacts/filters/{filter_id} Show contacts that meet the criteria of a filter
Returns the contacts matching a saved filter, alongside the filter's own definition. Results come back in Action Stream order and are fixed at 25 per page — per_page is accepted but ignored here.
Path parameters
| Name | Type | Description |
|---|---|---|
filter_id req | string | Filter ID |
Responses
200 OK
statusintegerint32Response code
messagestringResponse message
timestampintegerunix-timestampResponse time
dataobjectobject fields →
filterobjectAllow you to query contacts in your own custom way. These filters can only be created on the website but they can be used through the API.
object fields →
idstringbson-idID of the custom filter
namestringName of the custom filter
conditionsarray<array<string>>Conditions of the custom filter
total_countintegerint32Total number of items
pageintegerint32Current page number
per_pageintegerint32Number of items returned in each page
max_pageintegerint32The page number of the last page of items
contactsarray<object>array item fields →
contactobjectInformation about the people you are actively trying to sell to, and related sub-resources like Actions, Deals, Notes, Calls and Meetings.
object fields →
idstringbson-idID of the contact
titlestringThe title of the contact
enum: Mr · Mrs · Ms
first_namestringFirst name of the contact
last_namestringLast name of the contact
job_titlestringJob title of the contact
starredbooleanIs the contact starred?
photo_urlstringURL of the contact's photo
company_idstringbson-idID of the company, to which the contact belongs
company_namestringName of the company, to whom the contact belongs
urlsarray<object>URLs associated with the contact
array item fields →
typestringThe type of URL
enum: website · blog · twitter · linkedin · xing · facebook · google_plus · other
valuestringThe URL associated with the contact
phonesarray<object>Phone numbers associated with the contact
array item fields →
typestringThe type of phone number
enum: work · mobile · home · direct · fax · company · other
valuestringThe phone number associated with the contact
emailsarray<object>Email addresses associated with the contact
array item fields →
typestringThe type of email address
enum: work · home · other
valuestringThe email address associated with the contact
address_listarray<object>An array of contact addresses.
array item fields →
addressstringStreet address.
citystringCity.
statestringState, province or region.
zip_codestringPostal or ZIP code.
country_codestringISO 3166 country code, upper-case.
typestringType of the address
enum: work · home · billing · delivery · other
statusstringStatus of the contact
status_idstringbson-idID of the status of the contact
tagsarray<string>Tags on the contact — free-form strings from the account's tag list.
lead_source_idstringID of the lead source of the contact
lead_sourcestringDisplay name of the lead source of the contact
backgroundstringBackground infomation about the contact
owner_idstringbson-idID of the user, to whom the contact belongs. Defaults to the logged API user's ID.
custom_fieldsarray<object>Custom field values on the contact, as custom field and value pairs.
array item fields →
custom_fieldobjectExtra user-configurable data fields for Contacts. Only editable by admins.
object fields →
idstringbson-idID of the custom field
namestringrequiredName of the custom field
typestringrequiredType of the custom field. There are several types of custom fields that may store data in different formats. External ID type is a special type introduced for referencing entities in the external systems. Its value is unique amid the whole system. Section divider type is introduced just for visual purpose: it allows grouping custom fields. If custom fields in the section don't have values then they are hidden in the 'view' UI (but always shown in 'edit' UI). This logic is applied in the API: if a contact doesn't have values for all the custom fields in the section then this section divider custom field isn't exposed in the API (along with other custom fields inside the section).
enum: anniversary · date · multi_line_text · multiple_choice · number · select_box · single_line_text · external_id · section_divider
positionintegerint32The position of the custom field in the list
choicesarray<string>A list of possible choices (for fields of type `multiple_choice` or `select_box`)
valuestringValue for the custom field
letterstringThe first letter of the contacts last name
pending_dealbooleanDoes the contact have one or more pending deals?
total_pendingsnumberThe total value of all pending deals for the contact
total_deals_countintegerint32Number of deals associated with the contact
company_sizeintegerint32Number of contacts within the contact's company
sales_closed_forarray<string>A list of user IDs, for whom the sales cycle is closed
closed_salesarray<object>A list of closed sales objects
array item fields →
user_idstringbson-idID of the user, for whom the sales cycle is closed
closed_atintegerunix-timestampTime that the sales cycle was closed
commentstringAn optional message detailing why the sales cycle was closed
google_contacts_dataobjectThe google contacts data associated with this contact
object fields →
account_emailstringGoogle contacts email
idstringGoogle contact id
saved_atintegerunix-timestampTime the contact was saved to google
created_atstringdate-timeCreation time of the contact
modified_atstringdate-timeLast modification time of the contact
Standard error responses: 400 · 401 · 403 · 404 · 409 · 500 — shared across the API. See Errors.