Introduction
Buzzbip inbox conversations map to contact records. There is no public JWT REST endpoint to assign an agent yet. The closest mechanism is POST /inbox/v2/assign (session-authenticated inbox API): pass conversation_id (contact id), new_assignee_id, and an optional internal_note.
Steps
Follow this flow to assign a conversation from your integration or automation.
- Authenticate: POST /api/login_check for JWT (contact lookup) and maintain a Buzzbip web session cookie for inbox routes.
- Find the conversation: GET /api/contacts/?number=21696816277 — conversation_id is the Buzzbip contact id.
- List agents (optional): GET /inbox/v2/agents with session cookie to resolve new_assignee_id.
- Assign: POST /inbox/v2/assign with conversation_id, new_assignee_id, and optional internal_note.
- Verify: confirm assigned_agent_id in the JSON response, or re-fetch the contact via GET /api/contacts/.
Code example
Assign a contact conversation to agent id 42. Requires an active Buzzbip session (Cookie) — not Bearer JWT alone.
curl -X POST 'https://app.buzzbip.com/inbox/v2/assign' \
-H 'Content-Type: application/json' \
-H 'Cookie: PHPSESSID=your_session_cookie' \
-d '{"conversation_id": 745808, "new_assignee_id": 42, "internal_note": "VIP customer"}'conversation_id equals the contact id returned by GET /api/contacts/. Pass new_assignee_id: null to unassign.
What's next?
Related: api/contacts guides/send-whatsapp-message api/v1/automations
