Skip to main content
GET
List resources for an end user, optionally filtered by provider

Authorizations

Authorization
string
header
required

Enter your API key with the Bearer prefix — e.g. Bearer sk_live_xxx (production) or Bearer sk_test_xxx (sandbox)

Headers

X-End-User-Id
string
required

Identifier of the end user whose connected provider should be queried. This is the same endUserId you supplied when creating the connect token. Required on every CRM and accounting call.

Example:

"user-001"

Path Parameters

resource
enum<string>
required

Canonical CRM resource type to query. Must be one of the values in the enum below. RouteMCP maps this to the equivalent provider-native object (e.g. contact → HubSpot Contacts, Pipedrive Persons, Zoho Contacts).

Available options:
contact,
lead,
deal,
meeting,
owner,
company,
note,
task,
pipeline,
activity,
appointment

Query Parameters

provider
string

Provider slug to scope the query to a single connected provider (e.g. hubspot, pipedrive, zoho-crm, quickbooks-online, xero, zoho-books). When omitted, RouteMCP fans out across every provider the end user has connected and returns a merged, paginated result.

Example:

"hubspot"

cursor
string

Opaque pagination cursor returned in the previous response's top-level pagination.cursor field. Pass it back unchanged to fetch the next page. Omit on the first request.

Example:

"eyJodWJzcG90IjoiMTAwIn0"

limit
string

Maximum number of records to return per page. Defaults to the provider's native page size (typically 25–100) when omitted. Values are clamped to each provider's supported maximum.

Example:

"25"

enrich
string

Controls enrichment of related-record fields such as owner_name, owner_email, contact_name, companyName, etc. Accepts:

  • true (default) — enrich all supported fields. Adds extra provider calls; slower but more complete.
  • false — skip enrichment entirely. Fastest; returns only ids for related records.
  • A comma-separated list of field names (e.g. owner_name,owner_email) — enrich only the listed fields.
Example:

"true"

Response

Paginated list of CRM resources

Standard envelope returned by GET /crm/{resource}. The shape of each item inside data depends on the {resource} path parameter — see the tabs to switch between resource variants.

success
boolean
required

Always true for successful (2xx) responses.

Example:

true

statusCode
integer
required

HTTP status code mirrored inside the envelope.

Example:

200

message
string
required
Example:

"OK"

data
(Contact · object | Lead · object | Deal · object | Meeting · object | Owner · object | Company · object | Note · object | Task · object | Activity · object | Pipeline · object | Appointment · object)[]
required

The list of CRM resources. The item shape depends on the {resource} path parameter.

A person record (typically associated with a company/account).

pagination
Pagination · object
required

Cursor-based pagination metadata returned with every list response.