IngressController_receive_post
POST/api/ingress/:pluginId/:instanceId/:path
IngressController_receive_post
Request
Responses
- 200
- 202
- 400
- 401
- 403
- 404
- 413
- 415
- 429
- 503
GET verification challenge echo, or a route whose declared ack sets 200. Not the primary success path; see 202. A re-delivery that reaches the dedup check is answered with the route's ack (same status and headers as the first delivery), so it is not distinguishable by status.
Webhook accepted and queued for async plugin processing (the primary success path).
The path or query contains an encoded NUL (%00), or a JSON body does not parse.
Signature verification failed (missing, stale, or wrong secret).
GET verification challenge failed (verifyToken mismatch).
Unknown pluginId/instanceId, or no route claimed by the plugin.
Request body exceeds the route maxBodyBytes limit.
Request body is not application/json or application/x-www-form-urlencoded.
Rate limit exceeded: the per-instance bucket (INGRESS_INSTANCE_LIMIT) or the per-client-IP bucket (INGRESS_IP_LIMIT). The Retry-After-instance / Retry-After-ingress-ip header names which one shed the request, and a plain Retry-After carries the same delay for a client that reads only the standard name.
A route whose response contract declares a session-alive preflight, when the bound session has no running engine or its engine has failed (a starting, reconnecting or QR-pending session is answered with the route's ack). The delivery is not persisted, so the provider's retry is treated as a new one; Retry-After carries the delay.