This instance couldn't reach its API specification on the last attempt, so this page shows the copy fetched before that. Anything added or changed since then is missing here, and the reference updates itself as soon as the specification is readable again. Last fetched 2026-10-22 22:09 UTC.
The canonical event type string this schema describes.nullable
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
hasRichPayloadrequired
boolean
True when the event delivers a structured `data` object (an aggregate-backed event such
as a transaction completion). False for events that deliver only the flat `attributes`
map: for those, `dataFields` is empty and the sample shows the flat shape.
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
The schema of the `data` object's fields, generated from the payload CLR type via the
same exclusion logic the runtime projector uses. Empty when `hasRichPayload` is false.nullable
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
Fields of each WebhookPayloadSchemaField:
Field
Type
Description
namerequired
string
The JSON field name (the CLR property name, emitted verbatim by the projector).nullable
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
typerequired
string
The JSON type the value serializes as. One of the values in
`WebhookPayloadSchemaTypes`: `string`, `integer`, `number`,
`boolean`, `datetime`, `object`, or `array`.nullable
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
nullablerequired
boolean
Whether the field can be `null` / absent. Reference types and `Nullable`
value types are nullable; non-nullable value types are not. This is a best-effort hint derived
from the CLR type, not a guarantee that the field is always populated.
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
descriptionrequired
string
A curated, integrator-facing note about this field, or `null` when its name and
type say enough. Sourced from `WebhookPayloadFieldDescriptions` by the field's
dotted path, so the catalog and the delivered payload still come from one traversal.nullable
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
For `type` == `array`: a descriptor for the array's element. The element
descriptor's `name` is empty. Null for non-array fields.
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
truncatedrequired
boolean
True when the describe walk stopped at this node because the recursion-depth ceiling or a
type cycle was hit. The actual delivered payload carries a `__truncated` marker in the
same place. Defensive guard: not expected on today's tree-shaped aggregates.
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
This body has no documented fields.
sampleEnvelopeJsonrequired
string
A pretty-printed, illustrative sample of the full webhook envelope (id, type, version,
createdUtc, scope ids, correlationId, data) with placeholder values. For display only:
the values are synthetic, the shape is real.nullable
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
This response has no documented body fields.
defaultThe request failed. The body carries the standard error envelope: a machine-readable `error.code`, a human-readable `error.message`, and `error.validationErrors` when the failure was a validation rejection. The error reference lists the values `error.code` can take.The request failed. The body carries the standard error envelope: a machine-readable `error.code`, a human-readable `error.message`, and `error.validationErrors` when the failure was a validation rejection. The error reference lists the values `error.code` can take.
Values:Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
This response has no documented body fields.
429The request was refused because a rate limit was exceeded, or because something a later retry can clear stopped it. A rate limit refusal carries an `application/problem+json` body: wait at least the interval `Retry-After` names before retrying, then back off. Limits are tuned per deployment, so read the allowance from the response headers rather than assuming a fixed ceiling. Any other refusal carries the standard error envelope as `application/json`, and its `error.code` names the cause.