Skip to content
JawibDocumentationWHATSAPP API · v2
Documentation/Conversations

Conversations

Enable inbox_enabled and subscribe to message.received on the customer's webhook endpoint. Use the conversations API to retrieve retained messages and catch up after missed events.

Jawib returns content captured after inbox activation, within the retention period. The API does not provide an unrestricted export of a number's entire prior WhatsApp history.

Incoming content and media

Message resources expose text, media metadata, and supported interaction metadata as received from WhatsApp. Download private-message media using the same customer's key with media:read:

GET /api/v2/conversations/{conversation}/messages/{privateMessage}/media
Authorization: Bearer JAWIB_API_KEY

This endpoint returns a file. Download it from your backend, or expose it through an authorized route in your own application. Never embed an API token into an image or download URL.

Conversation reply modes

external delegates automation to your application. human pauses automated replies for a staff handoff. internal is unavailable on infrastructure connections.

When sending a staff reply, use sender_type: human and include the conversations:write scope. Resume automation explicitly by changing the conversation back to external.

Catch-up processing

Maintain a cursor per conversation. Process incoming events idempotently, and distinguish inbound messages from outbound synchronization events to avoid response loops. Expired content and excluded view-once or disappearing content are not available for download.

List conversations

GET/api/v2/conversations
Key owner: Customer or direct companyRequired scope: conversations:read
curl --request GET "https://playjawib.com/api/v2/conversations" \
  --header "Authorization: Bearer $JAWIB_API_KEY" \
  --header 'Accept: application/json'
Response example 200
{
    "data": [],
    "next_after_id": null
}

Illustrative values. Use the actual identifiers and credentials returned by your request.

List conversation messages

GET/api/v2/conversations/{conversation}/messages
Key owner: Customer or direct companyRequired scope: conversations:read

Replace {conversation} with the actual IDs returned by the API.

curl --request GET "https://playjawib.com/api/v2/conversations/{conversation}/messages" \
  --header "Authorization: Bearer $JAWIB_API_KEY" \
  --header 'Accept: application/json'
Response example 200
{
    "data": [],
    "next_after_id": null
}

Illustrative values. Use the actual identifiers and credentials returned by your request.

Update conversation reply mode

PATCH/api/v2/conversations/{conversation}
Key owner: Customer or direct companyRequired scope: conversations:write

Replace {conversation} with the actual IDs returned by the API.

curl --request PATCH "https://playjawib.com/api/v2/conversations/{conversation}" \
  --header "Authorization: Bearer $JAWIB_API_KEY" \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/json' \
  --data '{
    "reply_mode": "human"
}'
Request body fields
FieldTypeDescription
reply_moderequiredstringinternal / external / human
Response example 200
{
    "data": {
        "id": "42",
        "connection_id": "019c0000-0000-7000-8000-000000000002",
        "chat_jid": "249900000000@s.whatsapp.net",
        "contact_name": "Example Contact",
        "reply_mode": "human",
        "last_message_at": "2026-10-29T09:00:00+00:00"
    }
}

Illustrative values. Use the actual identifiers and credentials returned by your request.

Jawib API documentationAPI v2 · HTTPS / JSON
Search guides and API endpoints · Press Esc to close