Send message (or message_text) and identify the target with conversation_id or phone_e164. conversation_id is recommended because unmatched phone requests currently fall back to the first customer conversation for demo use.
Use an explicit target
Always pass conversation_id in production integrations.
POST/api/v1/messages/send
Auth:
Bearer sk_live_...Request Parameters
| Field | Type | Required | Description |
|---|---|---|---|
| conversation_id | UUID | Optional | Preferred target |
| phone_e164 | string | Optional | Phone target; recipient_phone and phone are aliases |
| message | string | Required | Text; message_text is an alias |
| media_url | string | Optional | Optional media URL |
Live Interactive API Playground
POST
/api/v1/messages/sendRequests 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/messages/send \
-H "Authorization: Bearer $PARRISCOPE_API_KEY" -H "Content-Type: application/json" \
-d '{"conversation_id":"CONVERSATION_UUID","message":"Your site visit is confirmed."}'