Authorization
apiKey In: query
Path Parameters
Request Body
application/json
Response Body
application/json; charset=utf-8
curl -X POST "https://api.getventia.com/api/v1.0/contact/string/archive" \ -H "Content-Type: application/json" \ -d '{ "reason": "sintrabajo" }'{
"archive": {
"content": {
"from": "",
"to": "notclient"
},
"_id": "646d13f254f8f1d196927794",
"company": "609b3cff61ffd5f1e446d234",
"agent": "6234da84259c59d9a555c498",
"contact": "621e8a5463c02a8bd532ff8c",
"status": "started",
"via": "api",
"createdCoords": {
"active": false
},
"type": "archiving",
"createdAt": "2023-05-23T19:28:50.867Z",
"updatedAt": "2023-05-23T19:28:50.867Z",
"__v": 0
}
}Get groups
Previous Page
Create message
Sends an outgoing message to a contact through any supported channel or personal WhatsApp session. Exactly one send-target must be provided in the body: - `channelId` — send through a shared channel (`unofficial_wpp`, `whatsapp_business`, `fb`, or `ig`). - `userId` + `medium` — send through a user's personal WhatsApp session. `medium: "unofficial_wpp"` uses the agent's Baileys session; `medium: "whatsapp_business"` uses their active Meta Cloud (WhatsApp Business) integration. - `userIntegrationId` — send through a specific WhatsApp Business personal integration by ID (shortcut for `userId` + `medium: "whatsapp_business"` when the integration is already known). The message content itself is one of: plain `text`, media (`mediaType` + `mediaUrl`), or an approved WhatsApp Business `template` ID. Templates are only supported on `whatsapp_business` channels and on personal WhatsApp Business integrations — they are rejected on unofficial (Baileys) sessions. The legacy `whatsapp_360_dialog` channel type is no longer supported.