Skip to main content
POST
Create or upsert a contact

Authorizations

Authorization
string
header
required

API key from Developer dashboard (Bearer token).

Body

application/json
first_name
string
last_name
string
name
string

Full name; derived from first/last when those are sent.

email
string<email>
phone
string
company
string
role
string
status
enum<string>
Available options:
active,
prospect,
in_progress,
lost
timezone
string
language
string
source
string
address1
string

Street line.

Maximum string length: 255
Example:

"12 Ermou St"

city
string
Maximum string length: 100
Example:

"Athens"

state
string

State, region or province.

Maximum string length: 100
Example:

"Attica"

postal_code
string

Text, not a number - leading zeros and letters are kept ("02134", "SW1A 1AA").

Maximum string length: 20
Example:

"10563"

country
string

ISO 3166-1 alpha-2 code ("GR") or an English country name ("Greece"); stored and returned as the code. An unknown country is a 422.

Example:

"GR"

date_of_birth
string<date>

YYYY-MM-DD (DD/MM/YYYY also accepted). A real past date after 1900; anything else is a 422.

Example:

"1985-03-14"

website
string

A bare domain gets https:// added.

Maximum string length: 500
Example:

"https://example.com"

tags
string[]
attributes
object

Custom attribute values keyed by attribute key.

list_source
enum<string>

Optional. Where these contacts came from. Leave it out and the contact is not marked (as before). bought, found_online and lead_finder make the contact outreach only: it is never emailed through the built-in email service, only through your own mail server. own_customers and events need list_consent: true. Every email also gets a free check (format, throwaway domains, domains that accept no mail, your suppression list); an invalid address is never emailed.

Available options:
own_customers,
events,
bought,
found_online,
lead_finder

Required as true when list_source is own_customers or events: these people agreed to receive email from you. Ignored for the other sources.

Response

Existing contact updated (matched by email)

success
enum<boolean>
Available options:
true
data
object
meta
object