callback URL you provided in POST /application/connect. Bringin appends the event path to your URL.
Example: If your callback is https://yourapp.com/bringin-webhooks, you’ll receive:
https://yourapp.com/bringin-webhooks/verification-statushttps://yourapp.com/bringin-webhooks/order-statushttps://yourapp.com/bringin-webhooks/connection-status
/verification-status
Fires when a user completes KYC or confirms connection to your app. This is how you get the per-user api-key.apikey — this is the per-user key you’ll use for all user-level API calls.
/order-status
Fires onSUCCESSFUL and FAILED order status changes.
| Field | Description |
|---|---|
orderId | Bringin transaction ID |
status | SUCCESSFUL or FAILED |
sourceId | Your reference ID (if you set one) |
sourceAmount | Amount sent (in smallest unit) |
destinationAmount | Amount received (EUR in cents) |
/connection-status
Fires when a connection becomes active (after user confirms SMS OTP).| Field | Present when |
|---|---|
depositIban | Buy connections (FIAT_TO_CRYPTO) |
depositAddress | Sell connections (CRYPTO_TO_FIAT, on-chain) |
lnAddress | Sell connections (CRYPTO_TO_FIAT, Lightning) |
Handling Webhooks
- Respond with
200quickly — process async if needed - You may receive the same webhook more than once — use
orderIdorbringinLinkIdas an idempotency key - If you didn’t provide a
callback, no webhooks are sent — use polling instead