Reject a ringing incoming call
POST/api/sessions/:sessionId/calls/:callId/reject
Reject a ringing incoming call
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 501
- 503
Call rejected
Session is not started
The API key is missing, unknown, revoked, or expired
The API key's role, session or chat scope, or IP allow-list does not allow this operation
Call not found or no longer ringing
The session is not connected: an engine exists for it but is not ready, meaning disconnected, reconnecting, or still initializing, so the request never reached WhatsApp. Wait for ready and retry. A session that was never started answers 400 instead, and the session lifecycle routes answer 409 for a conflicting state rather than this. One window answers this while the session still reads ready: WhatsApp Web periodically reloads its own page and the engine re-injects into it, and for those few seconds the answer is a 409 naming the reload; retry shortly.
The active engine cannot reject a call (whatsapp-web.js)
WhatsApp did not answer within the request budget. The change may or may not have been applied — the gateway stopped waiting for a confirmation that never came.