Start workflow execution
Start a new execution of a workflow asynchronously. The workflow will begin processing in the background.
You’ll receive a 202 Accepted response with a tracking_id immediately. Use this tracking_id to:
- Poll GET /workflow_executions with tracking_id filter to check status
- Correlate execution events with your own systems
The execution will fail if:
- The workflow is not in ‘active’ status
- Both phone_number and recipient are missing, or recipient is not a valid BSUID or parent BSUID
- recipient is used with a sandbox WhatsApp number
- The workflow definition is malformed
Use cases:
- Start workflow from external trigger (API, webhook, scheduled job)
- Test workflow with specific initial variables
- Retry failed execution with same parameters
Burst rate limit: This endpoint has an additional per-workflow burst limiter on top of the general platform API rate limits. The burst counter is scoped by API key and workflow ID and resets every second.
legacy/free: 5 requests per secondpro: 15 requests per secondenterprise/platform: 30 requests per second
Successful responses include X-Burst-RateLimit-Limit and X-Burst-RateLimit-Remaining headers.
If the burst limit is exceeded, the API returns 429 Too Many Requests with Retry-After: 1.
Body
Response
Workflow execution queued successfully (processing in background)
Async workflow execution initiation response (HTTP 202)

