Documentation / Complete
Your customers' sign-up cases and «Handled»
GET /v1/onboarding-cases
Building with AI? Connect it to your account over MCP: it checks your setup, creates webhooks and templates with your confirmation and writes the code for you. See how →
When a customer of one of your links gets stuck and writes on the signup screen, a case is born (A-<n>, the same data.caseId of onboarding.help_requested). It carries what they wrote verbatim, Meta's code, the diagnosis (from the catalog or by AI, with its confidence) and whether they uploaded a screenshot.
List them. GET /v1/onboarding-cases?status=open (default), acked or all; newest first.
Mark one handled. POST /v1/onboarding-cases/{id}/ack, once you sorted it out. It is idempotent. A 2xx webhook delivery does not count as handled.
In the dashboard. Your clients' sign-ups (shows in the menu once you created links): one row per link with its state (waiting, failed, connected, expired), the attempts, the last reason, the diagnosis, the text and the screenshot, the «Handled» button and, if it expired, «Generate a new link». Filters: Need attention (default), All, Connected.
# 1) the open cases (default status=open; also acked | all)
curl "https://api.waiaconnect.com/v1/onboarding-cases?status=open" -H "Authorization: Bearer wc_live_YOUR_API_KEY"
# → { "cases": [ { "id": "A-41", "status": "open", "externalId": "pharmacy-42",
# "clientText": "…", "metaErrorCode": 3441060, "diagnosis": { "title": "…", "responsible": "client", … } } ] }
# 2) once you sorted it out: mark it handled (idempotent)
curl -X POST https://api.waiaconnect.com/v1/onboarding-cases/A-41/ack -H "Authorization: Bearer wc_live_YOUR_API_KEY"A case of another account returns the same 404 ONBOARDING_CASE_NOT_FOUND as one that does not exist.
A status other than open, acked or all returns 400 ONBOARDING_CASE_STATUS_INVALID.
?lang=es|en|pt|it picks the language of a catalog diagnosis (default: the link's).