Create a new resource

curl --request POST \ --url https://api.routemcp.io/api/v1/crm/{resource} \ --header 'Authorization: <api-key>' \ --header 'Content-Type: application/json' \ --header 'X-End-User-Id: <x-end-user-id>' \ --data ' { "first_name": "Jane", "last_name": "Doe", "email": "jane.doe@example.com", "phone": "+1-555-0100", "job_title": "VP of Sales", "address": { "street_1": "123 Main St", "city": "San Francisco", "state": "CA", "postal_code": "94105", "country": "US" } } '

{ "success": true, "statusCode": 201, "message": "Created", "data": { "id": "12345", "remote_id": "12345", "first_name": "Jane", "last_name": "Doe", "email": "jane.doe@example.com", "phone": "+1-555-0100", "job_title": "VP of Sales", "address": { "street_1": "123 Main St", "city": "San Francisco", "state": "CA", "postal_code": "94105", "country": "US" }, "lifecycle_stage": "customer", "owner": "67823451", "owner_name": "John Smith", "owner_email": "john.smith@acme.com", "source": null, "remote_created_at": "2025-01-15T10:00:00.000Z", "remote_updated_at": "2025-03-01T14:30:00.000Z" } }

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 create. 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). owner and pipeline are read-only and cannot be created.

Available options:

contact,

lead,

deal,

meeting,

company,

note,

task,

activity,

appointment

Query Parameters

provider

string

required

Provider slug identifying which connected provider to target (e.g. hubspot, pipedrive, zoho-crm, quickbooks-online, xero, zoho-books). Required — single-record operations always target a specific provider.

Example:

"hubspot"

Body

application/json

CRM resource body. Pick an example from the dropdown to see the schema for each resource type.

first_name

string

Given name of the contact.

Example:

"Gil"

last_name

string

Family name of the contact.

Example:

"Feig"

account

string

Provider-native ID of the associated account (company). Format is provider-specific.

Example:

"420578000000250001"

owner

string

Provider-native ID of the record owner.

Example:

"420578000000250001"

addresses

Address · object[]

Postal addresses for this contact. Most providers persist only the first (primary) address.

Show child attributes

email_addresses

EmailAddress · object[]

Email addresses for this contact. The first entry is treated as the primary email.

Show child attributes

phone_numbers

PhoneNumber · object[]

Phone numbers for this contact. The first entry is treated as the primary phone.

Show child attributes

Response

Resource created successfully

Standard envelope returned by POST /crm/{resource}. Contains the newly created record. The shape of 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. 201 for successful creation.

Example:

201

message

string

required

Example:

"Created"

data

Contact · object

required

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

Show child attributes

Overview

CRM Resources

Workspaces

HTTP Streaming Chat

Accounting Resources

Field Mappings

Connect

Authorizations

Headers

Path Parameters

Query Parameters

Body

Response