Create Webhook
POST/public/api/v1/webhooks
Registers a new webhook endpoint limited to domains already approved on your point of sale configuration. A maximum of 10 active webhooks is allowed per merchant. Each webhook must subscribe to one or more supported events and include a shared secret used as the value of the Authorization header when sending webhook.
Webhooks are separate from the main payment flow and act as a general event notification system. You should use them only if you need to track changes to your ePay data in a system that is different from the one initiating the request.
For all payment-related operations, you should use the notificationUrl provided in each request. This is the primary mechanism for receiving the outcome of a payment or operation.
Request​
Responses​
- 200
- 400
- 422
- 500
Newly created webhook.
Standard error response returned when a request fails. Contains a machine-readable error code, a human-readable message.
Standard error response returned when a request fails.
Contains a machine-readable error code, a human-readable message,
and an errors object with field-specific validation issues.
Standard error response returned when a request fails. Contains a machine-readable error code, a human-readable message.