# Event Streams HTTP handler cannot access response (status/body) after POST/PUT

**URL:** <https://forum.inductiveautomation.com/t/event-streams-http-handler-cannot-access-response-status-body-after-post-put/114021>\
**Category:** Ignition\
**Created:** [February 18, 2026, 5:05am UTC](https://forum.inductiveautomation.com/t/event-streams-http-handler-cannot-access-response-status-body-after-post-put/114021 "2026-02-18T05:05:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sri\_Haran](https://avatars.discourse-cdn.com/v4/letter/s/c77e96/32.png) [@Sri\_Haran](https://forum.inductiveautomation.com/u/Sri_Haran)\
**Post date:** [February 18, 2026, 5:05am UTC](https://forum.inductiveautomation.com/t/event-streams-http-handler-cannot-access-response-status-body-after-post-put/114021/1 "2026-02-18T05:05:56Z")

</div>

Hello All,

In Ignition 8.3 Event Streams, the HTTP handler successfully sends POST/PUT requests, but there appears to be no way to access the HTTP response (status code, headers, or body) for use later in the stream. The Types of Handlers → HTTP docs list only request‑side properties (URL, method, headers, body, timeouts, cookies) and don’t show any response fields, which implies this isn’t supported: [Types of Handlers | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.3/ignition-modules/event-streams/types-of-handlers) (see “HTTP”).  
The general Event Streams overview also suggests handlers are terminal “do something” steps rather than payload‑transformers, which may be why responses aren’t exposed: [Event Streams | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.3/ignition-modules/event-streams)

**Question** : Is this by design for 8.3.x? If so, could Inductive consider a feature request to expose `statusCode`, `responseHeaders`, and `responseBody` so we can route based on response outcomes without switching to a Script handler?

**Workaround we’re using:** Replace the HTTP handler with a Script handler that uses `system.net.httpClient()` to perform the request and then forward a new event (including the response) via a Gateway Event handler to another stream.

**Best regards,**

Sri Haran S