Skip to main content
Webhooks fire to the 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-status
  • https://yourapp.com/bringin-webhooks/order-status
  • https://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.
Store the apikey — this is the per-user key you’ll use for all user-level API calls.

/order-status

Fires on SUCCESSFUL and FAILED order status changes.

/connection-status

Fires when a connection becomes active (after user confirms SMS OTP).

Handling Webhooks

  • Respond with 200 quickly — process async if needed
  • You may receive the same webhook more than once — use orderId or bringinLinkId as an idempotency key
  • If you didn’t provide a callback, no webhooks are sent — use polling instead