Create contact.

POST/api/v1/contacts

Browse API endpoints

Contacts / CRM REST API

Scope: contacts:write

Request body:

Code example

{
  "firstName": "Jane",
  "lastName": "Doe",
  "email": "jane@example.com",
  "phone": "+15551234567",
  "company": "Acme Corp",
  "lifecycleStage": "lead",
  "tags": ["website-lead"],
  "source": "api"
}

Field	Required	Description
`firstName`	Yes	First name
`lastName`	Yes	Last name
All other fields	No	See data model above

Side effects:

Fires contact.created webhook event
Triggers matching workflow automations
Validates custom field schemas if provided

Response: 201 Created with the full contact object.

Loading endpoint details...

Build a request

Request example

Documented defaults and example values are ready. Change only the parameters you need.

Connection

Your CRM deployment URL

Replace the Bearer API key placeholder in the copied server-side code. No API key is entered or sent here.

Sub-account ID Agency keys onlyAgency-scoped keys require the X-Sub-Account-Id header.

Body parameters

firstName Required - First name

lastName Required - Last name

phone

company

lifecycleStage

tags

source

Edit the full JSON body

cURL

curl --request POST \
  --url 'https://your-crm.example.com/api/v1/contacts' \
  --header 'Authorization: Bearer <YOUR_API_KEY>' \
  --header 'Content-Type: application/json' \
  --data '{"firstName":"Jane","lastName":"Doe","email":"jane@example.com","phone":"+15551234567","company":"Acme Corp","lifecycleStage":"lead","tags":["website-lead"],"source":"api"}'

This shows a static response from the documentation. It does not send a request to your CRM or use an API key.