Note: The terms message and event are used interchangeably in the documentation. In the context of this documentation, they both mean the same.
webhookie can receive events from your architecture via the Advanced Message Queueing Protocol (AMQP). The configuration for the AMQP setup is done in the Docker Compose File. Messages are sent to webhookie via a consumer queue. If there are validation errors with the message then webhookie will send the message back via a consumer missing header queue.
The following configurations can be added to your Docker Compose File to connect to your AMQP instance.
The consumer queue is where webhookie will consume the events.
If events, that webhookie receives, are missing the mandatory headers, wh-topic and content_type, it will return the message to the Consumer Missing Header Exchange with the Consumer Missing Header Routing Key. WH_CONSUMER_MISSING_HEADER_EXCHANGE=wh-consumer
Messages that are sent to webhookie can have any content type. webhookie does not validate the content type or the content so it is the provider’s prerogative to ensure that the content matches the content type and the schema definition documented in the ASYNC API specification. The messages can have the following headers:
Powered by BetterDocs