Digits · AsyncAPI Specification
Digits Com Webhooks
Version
View Spec
View on GitHub
AccountingBookkeepingFinanceGeneral LedgerArtificial IntelligenceFintechAsyncAPIEvents
AsyncAPI Specification
generated: '2026-07-18'
method: searched
source: https://developer.digits.com/reference/receivewebhookevent
type: Webhooks
status: private-beta
spec_type: none
description: >-
Digits sends webhook events as a JSON POST to a customer-configured endpoint; return any 2xx response
to acknowledge receipt (the response body is ignored). Webhooks are in private beta — early access via
developer@digits.com. Digits publishes an illustrative OpenAPI 3.0.3 "Digits Webhooks" schema (title:
Digits Webhooks) describing the WebhookEvent request body, but no AsyncAPI document is published.
delivery:
transport: http
method: POST
ack: any 2xx response; response body ignored
operation: receiveWebhookEvent
content_type: application/json
payload_schema: WebhookEvent
early_access_contact: developer@digits.com
reference: https://developer.digits.com/reference/receivewebhookevent
notes: >-
Captured as a Webhooks surface (no AsyncAPI spec exists, so none is fabricated). Event-type catalog
is not enumerated on the public reference during private beta.
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.
Call it yourself
curl for this page
This AsyncAPI spec
curl "https://apis.io/api/v1/asyncapis/digits-com-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.