Skip to content

Conversations

Download group members (CSV)

The group members list as a CSV download, in the same order and from the same cache. GET /api/conversations/{id}/participants?format=csv returns the same file.

GET/api/conversations/{id}/participants.csv
  • Bearer API key
  • Scope: read or write
  • or app session
  • Workspace: X-Tenant-ID (optional with a key)

Path parameters

  • iduuidrequired

    Conversation id of a group chat on a number connected by QR code.

    Example
    b2d4e6f8-0a1c-4e3a-8b5d-7f9a1c3e5b7d

Headers

  • Authorizationstringrequired

    Your API key as Bearer <key>. The word Bearer and the space are case-sensitive. Browser clients signed in to the app use the session cookie instead.

    Constraints
    Keys start with pk_live_ and are 56 characters long.
    Example
    Bearer pk_live_…
  • X-Tenant-IDuuidoptional

    Workspace id. Optional with an API key (a key always acts in its own workspace); if you send it, it must match the key’s workspace. Required with a session cookie. You can pass ?tenant=<id> instead.

    Example
    8d0f6c2e-3b1a-4c55-9a7e-2f4b6d1e9c30

Query parameters

  • refreshbooleanoptional

    Send 1 (or true) to ask WhatsApp again instead of using the stored list. Honoured at most once every 30 seconds per group; within that window you get the stored list (check fetched_at).

    Default
    0

Response

Status codes

  • 200OK. A text/csv; charset=utf-8 file with a UTF-8 byte order mark (so Excel reads every script), sent as an attachment named after the group, e.g. Wholesale-orders-members.csv. Columns: Name, Phone, Admin (Yes or No), WhatsApp ID. Cells that start with =, +, - or @ get a leading apostrophe so spreadsheets never run them as formulas; that is why phone numbers read '+15550100123.
  • 400Bad request. invalid conversation id; the conversation is not a group (Group members are only available for group chats); or the workspace uses Cloud API (Meta) numbers (Group members are only available for numbers connected by QR code).
  • 401Unauthorized. The API key is unknown, revoked or expired (invalid or expired API key), or there is no key and no signed-in session (unauthorized).
  • 402Payment required. Only when subscriptions are enforced and the workspace has no active subscription. The body includes code: "payment_required".
  • 403Forbidden. The X-Tenant-ID header or tenant query does not match the API key’s workspace (API key belongs to a different workspace), or a signed-in user is not a member of the workspace (forbidden).
  • 404Not found. The conversation does not exist in this workspace, belongs to the inactive connection (QR vs Cloud API), or (for agents signed in to the app) is not assigned to you. Also returned when WhatsApp no longer knows the group (WhatsApp could not find this group).
  • 409Conflict. The QR-linked number is not connected (whatsapp is not connected), or it is not a member of the group anymore (The connected WhatsApp number is not a member of this group anymore).
  • 502Bad gateway. WhatsApp did not answer. The failure is remembered for 10 seconds, so retry after that.
  • 500Server error. Something went wrong on our side. Retry with backoff.

Things to know

  • QR numbers only. Members are read from the WhatsApp linked by QR code. Cloud API (Meta) numbers get 400.
  • What WhatsApp shows a member, nothing more. Numbers WhatsApp hides from group members come back as ""; private (@lid) ids are mapped to a number only when WhatsApp has shared it with the linked phone.
  • Cached. WhatsApp is asked only when you call this endpoint (or open the members panel in the inbox), and the answer is kept for 10 minutes per workspace and group. ?refresh=1 asks again, at most once every 30 seconds per group. Lists do not update live when members join or leave.
  • Who can call it. API keys (a read key is enough) and workspace members. Agents signed in to the app only see groups assigned to them; other ids answer 404.
  • Read only. There is no endpoint to message every member of a group.