BRL · AsyncAPI Specification

Brl Webhooks

Version

View Spec View on GitHub CompanyCryptoStablecoinsPaymentsBrazilPixFintechBlockchainDigital AssetsWalletsYieldAsyncAPIEvents

AsyncAPI Specification

Raw ↑
generated: '2026-07-18'
method: searched
source: https://docs.crown-brlv.com/guides/webhooks-setup
spec_type: Webhooks
summary: >-
  Crown POSTs event notifications to a partner-configured endpoint URL. The
  provider publishes webhook definitions inside its OpenAPI 3.1 document
  (top-level `webhooks`) but ships no standalone AsyncAPI document. Every
  delivery is authenticated with an X-Crown-Signature HMAC-SHA256 header and
  must be acknowledged with a 200 OK within 5 seconds; failed deliveries may be
  retried automatically.
delivery:
  transport: https-webhook
  registration: Crown dashboard "Manage Users" -> Webhook URL -> Register Webhook (immediately active)
  auth:
    header: X-Crown-Signature
    scheme: HMAC-SHA256 of the raw request body using the account webhook secret
  ack: 200 OK within 5 seconds
  retries: automatic on failure (backoff not published)
  key_casing: kebab-case
envelope:
  required:
  - event-id      # uuid, unique per delivery
  - event-type    # kebab-case event name (see events[].event_type)
  - payload       # event-specific object
events:
- event_type: deposit-processed
  operation_id: depositProcessed
  summary: Deposit Processed
  description: >-
    A deposit was credited to the account. Covers fiat deposits (BRL via PIX or
    TED) and crypto deposits; a USDC/USDT/BRLV token transferred into one of the
    account's wallets is also treated as a deposit and carries the crypto payload
    variant with the asset and on-chain addresses.
- event_type: order-completed
  operation_id: orderCompleted
  summary: Order Completed
  description: A currency-conversion order has been successfully completed.
- event_type: token-transfer-completed
  operation_id: tokenTransferCompleted
  summary: Token Transfer Completed
  description: A token transfer sent from one of the account's wallets completed on-chain.
- event_type: withdraw-completed
  operation_id: withdrawCompleted
  summary: Withdrawal Completed
  description: A withdrawal (BRL PIX/TED or token) was successfully processed and sent.
- event_type: claim-completed
  operation_id: claimCompleted
  summary: Claim Completed
  description: A yield claim was processed and tokens were deposited.
- event_type: account-approved
  operation_id: accountApproved
  summary: Sub-account Approved
  description: >-
    A partner-initiated sub-account creation request cleared compliance and the
    sub-account was provisioned and activated. Fires on the parent account.
- event_type: account-rejected
  operation_id: accountRejected
  summary: Sub-account Rejected
  description: >-
    A partner-initiated sub-account creation request was not approved (rejected,
    expired, or cancelled). The reason is intentionally opaque and never
    discloses sanctions/KYC details. Fires on the parent account.
docs:
- https://docs.crown-brlv.com/guides/webhooks-setup
- https://docs.crown-brlv.com/api-reference/webhooks/deposit-processed

Work with this as data

Every AsyncAPI spec here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for asyncapi

4 MCP tools reach this
  • find_asyncapisBrowse and filter every AsyncAPI spec in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This AsyncAPI spec
curl "https://apis.io/api/v1/asyncapis/brl-webhooks"
All asyncapi
curl "https://apis.io/api/v1/asyncapis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.