POST API in Flow creator

0
Hi, I just wanted to confirm, if flow creator supports creating post api? because whenever I try to post to it, its always request timed out.what I feel is like the port 1880 is not made open? any specific reason for that?I believe a workaround that is to push my own node-RED instance container and expose that port, but not sure why flow-creator is blocked and is there any way to expose the same?
asked
1 answers
0

Hi Rohit,


Yes, you can create a POST API in Industrial Edge Flow Creator using Node-RED's HTTP In and HTTP Response nodes. However, the timeout does not necessarily mean that port 1880 is blocked.


Node-RED uses port 1880 by default, but Industrial Edge applications may be accessed through the device's reverse proxy rather than directly through the container port.


I would check the following:


1. Configure the POST endpoint

Create a flow with:

  • An HTTP In node configured for POST and a path such as /api/temperature.
  • Your processing nodes.
  • An HTTP Response node to return a response to the caller.

Deploy the flow and ensure that the HTTP Response node is reached for every request.


2. Use the correct Industrial Edge URL

When testing from outside the Flow Creator container, do not assume this URL will work:

http://<node-red-host>:1880/api/temperature

Depending on your Industrial Edge configuration, you may need to use the device address and the application-specific reverse-proxy path instead:

https://<IED-address>/<app-subpath>/api/temperature

Use the actual address and path provided by your Industrial Edge deployment. Do not guess the subpath.


3. Check the HTTP request

In Postman, use:

  • Method: POST
  • Header: Content-Type: application/json
  • Body → raw → JSON

Example body:

{"temperature": 27.3}

If authentication is enabled, provide the required credentials or token. If the device uses a certificate, ensure the client trusts it rather than disabling TLS verification in production.


4. Test and interpret the result

  • 404 Not Found: Check the URL path and confirm the deployed HTTP In node uses the same path and method.
  • 503 Service Unavailable: Check whether the Flow Creator app is running and whether the reverse proxy can reach it.
  • Timeout: Check network connectivity, routing, firewall rules, and whether the flow reaches the HTTP Response node.
  • 401/403: Check authentication and permissions.


5. Should you deploy your own Node-RED container?

Not necessarily. First verify whether Flow Creator already supports exposing the endpoint through the configured Industrial Edge route. Deploying a separate Node-RED container is an alternative only if you need control over networking or ports that the existing Flow Creator deployment does not expose.


References:


My recommendation: Test the endpoint through the URL provided by your Industrial Edge deployment first. The reverse-proxy path is a likely cause when a Node-RED flow works locally but cannot be reached through the edge platform.


Hope this helps! If you find this answer helpful, please mark it as the accepted answer.

answered