Integrations

List Crm Lists

Lists in the CRM.

Published as GET although the app spells it POST: every one of its parameters is a QUERY parameter and it reads. A POST that takes no body is a read wearing the wrong verb, and publishing it that way would put this behind a write grant for no reason.

get/integrations/crm/lists

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/integrations/crm/lists
  • Auth: HTTP bearer

Query parameters

connection_idstring required
querystring nullable

Filter by list name.

limitinteger
offsetinteger
entity_type'contacts' | 'companies' | 'deals' | 'leads'

Which object the list holds.

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Response

Successful Response

dataCrmPayload required

One CRM record, or one provider response.

Open-shaped ON PURPOSE. These bodies carry whatever the provider returned, the field set differs between HubSpot, Salesforce, Pipedrive and SugarCRM, and it grows every time one of them ships something. Pinning it would drop whatever a provider reported that this contract had not caught up on - which on a CRM surface means silently hiding the customer's own data from them.

Changes

No recorded changes to this operation across all 2 revisions of this API.