Omise · AsyncAPI Specification

Opn Ooo Webhooks

Version

View Spec View on GitHub CompanyPaymentsAPIFinTechSoutheast-AsiaAsyncAPIEvents

AsyncAPI Specification

Raw ↑
generated: '2026-10-25'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.omise.co/api-webhooks
sources:
- https://docs.omise.co/api-webhooks
- https://docs.omise.co/events-api
description: Omise webhooks are HTTP POST requests sent to an HTTPS endpoint when specific events occur. Each request includes an event object.
events:
- event: card.destroy
  description: Card has been destroyed
- event: card.update
  description: Card has been updated
- event: charge.capture
  description: Charge has been captured (manual capture only)
- event: charge.complete
  description: 'Charge has been completed successfully (Note: completing non-3DS card charges does not trigger this webhook)'
- event: charge.create
  description: Charge has been created
- event: charge.expire
  description: Charge has expired (Barcode Alipay only)
- event: charge.reverse
  description: Charge has been reversed (manual reversal only)
- event: charge.update
  description: Charge has been updated
- event: customer.create
  description: Customer has been created
- event: customer.destroy
  description: Customer has been destroyed
- event: customer.update
  description: Customer has been updated
- event: customer.update.card
  description: Card has been updated implicitly through a customer
- event: dispute.accept
  description: Dispute has been accepted
- event: dispute.close
  description: Dispute has been closed
- event: dispute.create
  description: Dispute has been opened
- event: dispute.update
  description: Dispute has been updated
- event: recipient.activate
  description: Recipient has been activated
- event: recipient.create
  description: Recipient has been created
- event: recipient.deactivate
  description: Recipient has been deactivated
- event: recipient.destroy
  description: Recipient has been destroyed
- event: recipient.update
  description: Recipient has been updated
- event: recipient.verify
  description: Recipient has been verified
- event: refund.create
  description: Refund has been created
- event: schedule.create
  description: Schedule has been created
- event: schedule.destroy
  description: Schedule has been destroyed
- event: schedule.expire
  description: Schedule has expired
- event: schedule.expiring
  description: Schedule will expire soon
- event: schedule.suspend
  description: Schedule has been suspended
- event: transfer.create
  description: Transfer has been created
- event: transfer.destroy
  description: Transfer has been destroyed
- event: transfer.fail
  description: Transfer has been marked as failed
- event: transfer.pay
  description: Transfer has been marked as paid
- event: transfer.send
  description: Transfer has been marked as sent
- event: transfer.update
  description: Transfer has been updated
delivery:
  signature: Signature verification is recommended; details are described in the Protecting Your Endpoints section. No specific header name is
    listed on the page.
  retries: The documentation does not specify a retry policy for webhook deliveries.
docs: https://docs.omise.co/api-webhooks

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/opn-ooo-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.