Create Contact
Getting Started
Create Contact
Add a new contact (lead) to your CRM, with optional attributes. Fails with 409 if the number is already a contact.
POST
Create Contact
Adds a lead to your CRM from your own system, such as a website form, an ad platform or your backend. The contact appears in the CRM straight away, with any attributes you send.
Quick Example
Use Cases
- Website forms: save a lead the moment someone submits a form
- Ad and lead platforms: push leads from your lead source into the CRM as they arrive
- Your own backend: create a contact when a customer signs up or places an order
Where to find the values
Phone numbers
to_number is saved as digits with the country code, the same way the CRM stores every contact:
- Spaces, dashes, brackets and
+are removed:+91 98765-43210is saved as919876543210. - A 10-digit number is treated as Indian, and
91is added:9876543210is saved as919876543210.
+919876543210, 919876543210 and 9876543210 are all the same contact.
How attributes are saved
Each row inattributes is a key and a value.
- Matching names:
keyis matched to your CRM attributes ignoring case, spaces, underscores and hyphens, so"First Name"matchesfirst_name. - Types: the value is checked against the attribute’s type. A number attribute needs a number, a date needs a date, a yes/no attribute needs
trueorfalse, and an enum value must be one of its options. - Limits: up to 50 rows per request, and each value at most 1000 characters. A value must be a string, number or boolean, not an object or a list.
Errors worth handling
409 Contact already exists
409 Contact already exists
The number is already a contact on this account. Use Update Contact to change its attributes.
401 Invalid API key
401 Invalid API key
The
X-API-KEY header is missing or does not belong to any account. Copy the key again from API Key in the dashboard.403 Account is inactive
403 Account is inactive
The account the key belongs to has been deactivated. Contact support.
400 Missing to_number, or a problem with attributes
400 Missing to_number, or a problem with attributes
The body has no phone number,
attributes is not a list, or a row has no key, an object or list as its value, or a value longer than 1000 characters. The message says which.Authorizations
API key from https://callkaro.ai/dashboard/api-key
Body
application/json
Phone number with country code. A 10-digit number is read as Indian (+91). Spaces, dashes and + are ignored.
Example:
"+919876543210"
CRM attributes to save on the contact. Only attributes that already exist in CRM > Attributes are saved.
Maximum array length:
50