Execution

When an event occurs, Loyale finds every subscription for the event's scheme and topic and independently delivers the topic payload to each registered URL.

Request

Item	Value
Method	`POST`
Content type	`application/json; charset=utf-8`
Accept header	`application/json`
Body	The JSON-serialized model documented on the topic page
Signature	No webhook-signature header is currently added

The payload is sent directly as the request body; it is not wrapped in a separate event envelope.

Success

Any HTTP response in the 200–299 range completes delivery. Loyale does not use the response body. Return success only after your system has durably accepted the event.

Failure

A non-2xx response or connection failure is recorded as an unsuccessful attempt and starts the retry flow. Each original delivery creates a webhook log containing the serialized payload, and every subsequent attempt is appended to that log.

Delivery characteristics

Multiple subscriptions to the same topic receive independent requests.
Some topic producers enqueue delivery as background work, while others await it directly. Do not rely on strict ordering.
Retries can cause duplicate deliveries. Receivers should be idempotent.
Delivery requests do not include the topic number separately; determine the event from the subscribed URL or the subscription configuration.

See Getting Started for receiver guidance and Retries for operational details.