APIHub

Back to Explore

CRM API

The CRM API offers unified CRUD operations for core CRM resources—including activities, companies, contacts, and leads—allowing you to list, create, retrieve, update, and delete these records across supported CRM services.

Development

apiKeyHeader

HTTPS

CORS: Unknown

Description enriched …

Visit official documentation

Latency

2558ms p95

Uptime

100.0% 30d

Playground

Verified

live

Endpoints

REST · JSON

GET

/crm/activities

List activities

raw (query) — Include raw response. Mostly used for debugging purposes
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
cursor (query) — Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response.
limit (query, limit) — Number of results to return. Minimum 1, Maximum 200, Default 20
filter (query) — Apply filters
fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.

POST

/crm/activities

Create activity

raw (query) — Include raw response. Mostly used for debugging purposes
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.

DELETE

/crm/activities/{id}

Delete activity

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes

GET

/crm/activities/{id}

Get activity

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes
fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.

PATCH

/crm/activities/{id}

Update activity

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes

GET

/crm/companies

List companies

raw (query) — Include raw response. Mostly used for debugging purposes
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
cursor (query) — Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response.
limit (query, limit) — Number of results to return. Minimum 1, Maximum 200, Default 20
filter (query) — Apply filters
sort (query) — Apply sorting
fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.

POST

/crm/companies

Create company

raw (query) — Include raw response. Mostly used for debugging purposes
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.

DELETE

/crm/companies/{id}

Delete company

id (path, required) — ID of the record you are acting upon.
raw (query) — Include raw response. Mostly used for debugging purposes
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.

GET

/crm/companies/{id}

Get company

id (path, required) — ID of the record you are acting upon.
raw (query) — Include raw response. Mostly used for debugging purposes
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.

PATCH

/crm/companies/{id}

Update company

id (path, required) — ID of the record you are acting upon.
raw (query) — Include raw response. Mostly used for debugging purposes
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.

GET

/crm/contacts

List contacts

raw (query) — Include raw response. Mostly used for debugging purposes
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
cursor (query) — Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response.
limit (query, limit) — Number of results to return. Minimum 1, Maximum 200, Default 20
filter (query) — Apply filters
sort (query) — Apply sorting
fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.

POST

/crm/contacts

Create contact

raw (query) — Include raw response. Mostly used for debugging purposes
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.

DELETE

/crm/contacts/{id}

Delete contact

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes

GET

/crm/contacts/{id}

Get contact

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes
fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.

PATCH

/crm/contacts/{id}

Update contact

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes

GET

/crm/leads

List leads

raw (query) — Include raw response. Mostly used for debugging purposes
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
cursor (query) — Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response.
limit (query, limit) — Number of results to return. Minimum 1, Maximum 200, Default 20
filter (query) — Apply filters
sort (query) — Apply sorting
fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.

POST

/crm/leads

Create lead

raw (query) — Include raw response. Mostly used for debugging purposes
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.

DELETE

/crm/leads/{id}

Delete lead

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes

GET

/crm/leads/{id}

Get lead

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes
fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.

PATCH

/crm/leads/{id}

Update lead

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes

GET

/crm/notes

List notes

raw (query) — Include raw response. Mostly used for debugging purposes
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
cursor (query) — Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response.
limit (query, limit) — Number of results to return. Minimum 1, Maximum 200, Default 20
fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.

POST

/crm/notes

Create note

raw (query) — Include raw response. Mostly used for debugging purposes
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.

DELETE

/crm/notes/{id}

Delete note

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes

GET

/crm/notes/{id}

Get note

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes
fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.

PATCH

/crm/notes/{id}

Update note

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes

POST

/crm/pipelines

Create pipeline

raw (query) — Include raw response. Mostly used for debugging purposes
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.

GET

/crm/opportunities

List opportunities

raw (query) — Include raw response. Mostly used for debugging purposes
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
cursor (query) — Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response.
limit (query, limit) — Number of results to return. Minimum 1, Maximum 200, Default 20
filter (query) — Apply filters
sort (query) — Apply sorting
fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.

POST

/crm/opportunities

Create opportunity

raw (query) — Include raw response. Mostly used for debugging purposes
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.

DELETE

/crm/opportunities/{id}

Delete opportunity

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes

GET

/crm/opportunities/{id}

Get opportunity

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes
fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.

PATCH

/crm/opportunities/{id}

Update opportunity

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes

GET

/crm/pipelines

List pipelines

raw (query) — Include raw response. Mostly used for debugging purposes
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
cursor (query) — Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response.
limit (query, limit) — Number of results to return. Minimum 1, Maximum 200, Default 20
fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.

DELETE

/crm/pipelines/{id}

Delete pipeline

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes

GET

/crm/pipelines/{id}

Get pipeline

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes
fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.

PATCH

/crm/pipelines/{id}

Update pipeline

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes

GET

/crm/users

List users

raw (query) — Include raw response. Mostly used for debugging purposes
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
cursor (query) — Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response.
limit (query, limit) — Number of results to return. Minimum 1, Maximum 200, Default 20
fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.

POST

/crm/users

Create user

raw (query) — Include raw response. Mostly used for debugging purposes
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.

DELETE

/crm/users/{id}

Delete user

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes

GET

/crm/users/{id}

Get user

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes
fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.

PATCH

/crm/users/{id}

Update user

id (path, required) — ID of the record you are acting upon.
x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
x-apideck-app-id (header, required) — The ID of your Unify application
x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
raw (query) — Include raw response. Mostly used for debugging purposes

40 endpoints auto-detected

Authentication

This API uses an API key, passed in the "Authorization" header. No OAuth required.

curl -X GET \
  "https://unify.apideck.com/crm/activities" \
  -H "Authorization: YOUR_API_KEY"

unify.apideck.com · HTTPS only