Endpoint Management
Last updated
Last updated
As a webhook subscriber, you have the ability to create new endpoints to suit your specific needs. In order to create a new endpoint, you must provide certain information such as a URL, a default version, a description, and set the status of the endpoint.
The URL is the address where the webhooks will be sent when the events occur, this is the destination where you want to receive the webhooks. The default version is the version of the webhooks that you want to receive by default, this way you can ensure that you are up-to-date with the latest features and functionality.
A description of the endpoint can help you identify the endpoint more easily and keep track of what it is for. Finally, setting the status of the endpoint allows you to enable or disable it as needed, this is particularly useful when you need to temporarily disable an integration.
View your endpoint to grab the endpoint ID, error rate, endpoint URL, signing secret, view and subscribe to webhook events and even send a sample payload for the event. As a webhook subscriber you have the ability to view your endpoint and access important information such as the endpoint ID, error rate, URL, signing secret, and more. This allows you to easily manage and keep track of your webhook subscriptions.
The endpoint ID is a unique identifier that can be used to track and manage the endpoint. Additionally, you can see the error rate, which can help you identify if there are any issues with the endpoint that need to be addressed.
You can also view the endpoint URL, which is the destination where the webhooks will be sent when the events get triggered. This can be useful if you need to check that the URL is correct or if you need to update it.
Here you also have the ability to subscribe/unsubscribe to specific webhook events, this way you can ensure that you are only receiving the information that is relevant to you, and that it is delivered to the right place. Furthermore, you can even send a sample payload for the event to test your endpoint.
As a webhook subscriber, you also have the ability to view your webhook logs. This feature allows you to easily track and monitor the status of your webhooks, and troubleshoot any issues that may arise.
You can filter the logs by different criteria such as succeeded or failed webhook attempts, event type, your unique event ID, error message, status code, or even the payload. This allows you to quickly and easily identify any webhooks that have not been delivered successfully, and to view the details of the specific error that occurred.
The event type filter allows you to see the type of event that was triggered, this can be useful to understand the context of the webhook. The unique event ID filter is used to track the event across different systems and ensure that you are looking at the correct event.
The error message filter allows you to see any error message that was generated during the webhook attempt, this can be useful to understand what went wrong and how to fix it. Additionally, the status code filter allows you to view the status code that was returned by the webhook, this can be useful to understand the outcome of the webhook attempt.
The payload filter allows you to view the payload that was sent during the webhook attempt, this can be useful to understand the data that was sent and check if it was the right data.
