Track events
If an event occurs in the tebio Business Portal that is relevant to a configured webhook, tebio generates an event. The Events tab serves as a central overview for monitoring webhook events, allowing you to understand which events were sent to your endpoints, when, and whether the transfer was successful.
When do I need this function?
Section titled “When do I need this function?”Use the webhook event log if you:
- Want to check whether a specific event (e.g. a change of address or a new order) was actually transmitted to your third-party system, for example CRM or ERP.
- You want to search for errors or carry out debugging because your third-party system did not receive data or received it incompletely.
- Want to get an overview of the number and type of events triggered.
Requirements
Section titled “Requirements”- You need administrative rights for the Developer area.
- You should already have at least one Webhook set up, otherwise no webhook events will appear in this overview.
Step-by-step instructions
Section titled “Step-by-step instructions”Navigation
Section titled “Navigation”- In the main navigation, click on the Terminal icon at the top right.
- Switch to the Events tab.
Filter and monitor events
Section titled “Filter and monitor events”In the standard view, you see a chronological list of all events generated for your endpoints.
Use the Status dropdown on the left to filter the list specifically:
- None: Removes the filter and shows all events.
- Notified: Shows all events that were successfully delivered to your webhook (HTTP status 200 OK).
- Scheduled: Shows events that are still in the queue and will be sent soon.
- Failed: Relevant for debugging and error analysis. Shows events where the delivery attempt failed (e.g. because your recipient server was offline or responded with an error code like 500). Note: tebio has an automatic retry logic and will attempt delivery several times in the event of errors.
Understand table
Section titled “Understand table”The table provides you with the most important metadata for each event:
- Event Date/Time: Time the event occurred in the portal.
- Notification Date/Time: Time the event was (successfully) sent to your webhook.
- Code Type: The technical name of the event (e.g.
customer.address.updateorsubscription.option.add). - Entity: The affected data object (e.g.
ADDRESS,SUBSCRIPTION). - Reference, ID or UID: The unique identifiers of the affected record that allow you or your system to retrieve the record via API.
Result
Section titled “Result”You can see which webhook events were generated, the status of the delivery and which records are affected.
API Notes
Section titled “API Notes”If you want to read the event log via the API or update the notification status of failed events, use the following endpoints:
| End point | Method | Description | OperationId |
|---|---|---|---|
/v1/event/webhook | GET | Search webhook events (filterable by status and date) | searchWebhookEvent |
/v1/event/webhook | PATCH | Update the notification status of a webhook event (e.g. to manually terminate retries) | updateWebhookEvent |