Create Webhook
Tell Finogate the single web address where it should send you automatic updates when things happen on your platform.
When you call this, you:
- Give us one web address (URL) where you want notifications sent
- Choose which events you want to hear about — specific ones, whole groups, or all of them
Your platform has exactly one webhook. If you have already set one up, calling this again simply replaces it — the web address and the chosen events — with the new details. It does not create a second webhook.
The first time you set up your webhook, the response also includes a
signing secret: a private key you use to confirm that a notification
really came from Finogate. The signing secret is shown only once, right
here in this response — save it somewhere safe, it cannot be shown again.
When you later update an existing webhook, no new secret is issued and the
secret field is empty.
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Body
Create a new webhook endpoint on the platform.
HTTPS URL that will receive webhook POST requests.
1 - 2048"https://example.com/webhooks"
Individual event types to subscribe to. An empty list subscribes to all events.
[
"payment_intent.succeeded",
"payment_intent.failed"
]Event groups to subscribe to (e.g. 'payment', 'wallet'). Expanded into individual event types and merged with events.
["payment", "compliance"]Optional human-readable description for the webhook endpoint.
255"Production payment notifications"
Response
Successful Response
Standard response wrapper for single-object responses and errors.
Generic over the payload type. A route that declares
CommonResponse[SomeModel] gets the real data schema rendered in
OpenAPI/Swagger; a bare CommonResponse leaves data untyped.

