Authorizations
Bearer HTTP authentication specified with the header Authorization: Bearer <access_token>
Headers
Specifies which version of the Monime API will handle this request.
caph.2025-08-23
, caph.2025-06-20
The value is the tenancy parameter that Monime uses to determine which space the request is intended for.
64
Path Parameters
Unique identifier of the webhook to update.
Body
Partially update an existing webhook's configuration and behavior.
Updated name for the webhook.
1 - 100
New URL to send webhook requests to.
255
Enable or disable the webhook.
Updated API release name for webhook payloads.
caph
, siriusb
Updated list of events that trigger the webhook.
1 - 100
elementsUpdated HTTP headers to include in webhook requests.
Updated alert email list for delivery failures.
2
Updated custom metadata for the webhook.
Response
OK
Represents the status of the query operation, confirming if it was successful. This field is always true
Contains a list of messages providing relevant information or feedback related to the query or operation
A Webhook is a user-defined HTTP endpoint that Monime invokes with a POST request whenever specific events occur, such as payment.completed
or payout.failed
.
Webhooks allow you to receive real-time notifications and integrate Monime’s event stream directly into your own systems.
Use Cases
-
Realtime Payment Updates
Receive an immediate notification when a payment succeeds and update your user’s dashboard without polling the API. -
Automated Payout Reconciliation
Trigger accounting workflows or ERP system updates when a payout is marked ascompleted
orfailed
. -
Fraud & Risk Monitoring
Stream payment events into your fraud detection system as they happen.