Matching uses phone, then email, then channel identity. A lead/timeline record is created even when the person already exists.
POST/api/v1/contacts
Auth:
Bearer sk_live_...Request Parameters
| Field | Type | Required | Description |
|---|---|---|---|
| name | string | Optional | Name or phone is required |
| phone_e164 | string | Optional | phone is an alias; 10 Indian digits become +91 |
| string | Optional | Secondary match | |
| source | string | Optional | Defaults to api |
| campaign | string | Optional | Attribution |
Live Interactive API Playground
POST
/api/v1/contactsRequests use your current ChatFleet workspace.The playground makes a real request to this workspace. Use a scoped test key; never paste a production secret into a shared browser.
The key is not saved by this page.
Enter a scoped key, then run the request to inspect the live response here.
Code Examples
curl -X POST http://localhost:8080/api/v1/contacts \
-H "Authorization: Bearer $PARRISCOPE_API_KEY" -H "Content-Type: application/json" \
-d '{"name":"Aarav Mehta","phone_e164":"+919833445566","source":"website"}'