HTTP Response

Ends an ingress pipeline by answering the caller. Sets the status code, the content type and the body from the message.

Type: rest-response · Category: API · Ports: one input · no output

When to use it

• Every path through an ingress pipeline — success and failure alike
• Returning a created record, or an error the integrator can act on

Settings

Setting	Key	Default	Purpose
Status	http_status	200	Response code.
Content type	content_type	application/json	Response content type.
Headers	http_headers	{}	Extra response headers.
Reply to	reply_to	—	Which ingress node this responds to.

Example — accepting or rejecting the order

REST API (ingress POST /api/v1/orders)
  → Python (validate)
  → SQL (insert)
  → HTTP Response (201)

with a second branch for the failure:

  → HTTP Response (400, body {{payload.error}})

Gotchas

• Every path needs one. A branch that ends without a response leaves the caller waiting for its own timeout — which looks like a network fault from the other side and is far harder to diagnose than an error code.

See also

• REST API