Two · AsyncAPI Specification

Two Webhooks

Version

View Spec View on GitHub CompanyB2B PaymentsFinTechAPI PlatformCheckoutTrade AccountsAsyncAPIEvents

AsyncAPI Specification

Raw ↑
generated: '2026-10-29'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.two.inc/llms/guides/order-webhooks-api-page.txt
sources:
- https://docs.two.inc/llms/guides/order-webhooks-api-page.txt
- https://docs.two.inc/llms/api/webhooks/two-webhooks.txt
- https://docs.two.inc/llms/openapi/webhooks-api.txt
- https://docs.two.inc/llms/api/checkout/notify-order-handler-post.txt
description: Two provides a set of webhook events for order reconciliation, order status, customer & credit, and other actions.
events:
- event: order.reconciliation.invoiced.v1
  description: Occurs when an order has been successfully fulfilled and the corresponding invoice has been created by Two.
- event: order.reconciliation.payment_allocated.v1
  description: Occurs when a payment is made and confirmed as allocated to a specific invoice or statement, or when a previously matched payment
    is deallocated.
- event: order.reconciliation.credited.v1
  description: Occurs when a credit is applied to an order.
- event: order.reconciliation.recoursed.v1
  description: Occurs when a recourse action is taken on an order.
- event: order.reconciliation.collected.v1
  description: Occurs when an order has been collected.
- event: order.verified.v1
  description: Occurs when an order is verified.
- event: order.fulfilled.v1
  description: Occurs when an order is fulfilled.
- event: order.cancelled.v1
  description: Occurs when an order is cancelled.
- event: order.refunded.v1
  description: Occurs when an order is refunded.
- event: order.rejected.v1
  description: Occurs when an order is rejected.
- event: customer.credit_limit.updated.v1
  description: Occurs when a customer's credit limit is updated.
- event: billing_statement.created.v1
  description: Occurs when a billing statement is created.
- event: instalments.invoiced.v1
  description: Occurs when instalments are invoiced.
- event: customer.in_arrears_block.v1
  description: Occurs when a customer is placed in an arrears block.
- event: customer.approaching_arrears_block.v1
  description: Occurs when a customer is approaching an arrears block.
- event: customer.exit_arrears_block.v1
  description: Occurs when a customer exits an arrears block.
- event: customer.exit_approaching_arrears_block.v1
  description: Occurs when a customer exits an approaching arrears block.
- event: customer.user.verified.v1
  description: Occurs when a customer's user is verified.
- event: merchant.payee_account.activated.v1
  description: Occurs when a merchant's payee account is activated.
- event: business_registry.approved.v1
  description: Occurs when a business registry entry is approved.
- event: business_registry.rejected.v1
  description: Occurs when a business registry entry is rejected.
delivery: {}
note: The documentation does not specify signature headers, authentication methods, or retry behavior for webhook deliveries. 10 extracted row(s)
  were dropped because their quote was not on the page.
docs: https://docs.two.inc/llms/guides/order-webhooks-api-page.txt

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/two-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.