> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/release-notes/archive/2022/2022-10-06-ce-webhooks.md).

# 2022-10-06: CE - Webhook Event Publishing

### Overview

Webhook Event Publishing is a new platform feature that allows our customers to move towards an event-driven architecture for integrating with other systems. This means that external systems can subscribe to internal events published by the Emporix Platform, such as when an order is created or a price updated. With webhooks, you do not need to call specific API endpoints to look for recent changes in services — you will be automatically notified instead.

### New features

| Feature                           | Description                                                                                                                                                                                                                                                                                                                                                                                          |
| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Event subscription management** | You need to subscribe to events, for example creating or updating a catalog in the Emporix API Catalog Service, to receive notifications about them. You can view existing subscriptions for a tenant.                                                                                                                                                                                               |
| **Event Gateway**                 | The Emporix webhook feature requires you to pre-configure an endpoint on the Event Gateway before you can receive events you have subscribed to. When an event that you subscribed to takes place, a message is sent to the Webhook Service. The service forwards the message to the Event Gateway, which then passes the event to the customer's pre-configured endpoint for this particular event. |

### Fixes and improvements

None as these are new services.

### Known problems

No known problems at the time of release.

### Documentation and links

* User Guide — [Webhook Event Publishing](/user-guides/system-management/webhooks-user-guide.md)
* Developer Guide — [Webhook Service](/api-documentation/api-guides/webhooks/webhook-service/webhooks-tutorial.md)
* API Reference — [Webhook Service](/api-documentation/api-guides/webhooks/webhook-service.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.emporix.io/release-notes/archive/2022/2022-10-06-ce-webhooks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.