Webhook

The Webhook connector is a field connector that lets an external system push values into Reniway over HTTP. Instead of Reniway polling a machine or subscribing to a broker, the other side calls the Reniway API whenever it has a new value.

Use it for systems that can only send data outwards, such as an ERP or MES that fires a webhook, a custom application, a script, or an IoT device that speaks plain HTTP.

Connection settings

This connector has no connection settings. You only need to create the connector and give it a name. All configuration happens on the properties and on the calling side.

Adding properties

Every property is defined manually and only needs:

Property field	Description
Name	Display name of the property.
Type	Reniway property type the incoming value must match, for example Double, String or JSON.

Properties are input properties: the value comes from outside. Note the property Id of each property, because the caller addresses the property by that id.

Pushing a value

Send an HTTP PUT to the value endpoint of the property:

PUT /bridges/{bridgeId}/properties/{propertyId}/value

The body is JSON:

{
  "value": "23.4",
  "measurementDateTime": "2026-09-22T09:31:00Z"
}

Field	Description
value	The new value, as a string. It must be convertible to the property's configured type.
measurementDateTime	Optional. The moment the value was measured, in UTC. When omitted, Reniway uses the time the request arrived.

A complete example with curl:

curl -X PUT \
  -H "X-Reniway-Token: <your application token>" \
  -H "Content-Type: application/json" \
  -d '{"value":"23.4"}' \
  https://<reniway-host>/bridges/12/properties/34/value

Authentication

The endpoint accepts either an authenticated user session or an application token, which is the right choice for machine-to-machine calls. Create one under Settings in the Application Tokens tab, give it the Connectors.Manage permission, and send it in the X-Reniway-Token request header.

Responses

Status	Meaning
200 OK	The value was accepted and stored.
404 Not Found	No webhook connector with that id, or the connector has no property with that id.
422 Unprocessable Entity	The value does not match the property's type. The response states the expected type.

Runtime behavior

• The connector holds no connection of its own, so it is always healthy once started.
• An incoming value is type-checked against the property's configured type before it is stored. A value that cannot be converted is rejected and logged, and the stored value stays unchanged.
• Once stored, the value behaves like any other property value: it can be mapped, used in flows and stream processing, and forwarded to enterprise connectors.

Notes

• This connector is input-only. Reniway does not call out to the other system; use the MQTT, SQL or Ultimo connectors for that direction.
• There is no polling interval, because nothing is polled. The update rate is entirely up to the caller.
• Values arrive exactly as the caller sends them, so the calling side is responsible for rate-limiting and for not sending duplicates.