evt_*) is Natural’s record that something happened on your account: each one names what occurred and carries a point-in-time snapshot of the resource it describes. A webhook (whk_*) is the URL events are pushed to; an event is the record itself. Events are what Webhooks deliver to your server. GET /events lists the same events on demand, and GET /events/{eventId} fetches one. Read them with an API key or user session holding party.read; to list a connected customer’s events, pass customerPartyId and eventType.
The event object
The API returns events as standard resources. TheeventType attribute names what happened, and the resource snapshot lives at payload.object:
Webhook deliveries carry the same event in a flat body: there, type names the event and the snapshot lives at data.object. See Webhooks for the delivery format, signature verification, and retries.
The Event catalog documents every event type and the full snapshot payload it carries.
For resources with a matching public GET endpoint, new event snapshots use the same resource shape: id, type, attributes, and any relationships. Money, statuses, timestamps, and missing values follow that resource’s API contract. The outer event ID and event type remain separate from the resource ID and resource type. Snapshots may also include the resource’s event version.
A snapshot records the resource at the event’s time and for the party receiving it. A later GET can show newer state. Recipient payment snapshots omit sender-only diagnostics and fees; a payment from an external sender has a null sender relationship.
Wallet balances and related metadata are captured when the public event is created. Wallet snapshots include deposit instructions, with bank account and routing numbers when available. Connected subscriptions receive wallet.created under the customer’s active connection consent; a separate wallets.read grant is not required for that event.
Invitation-link snapshots use the GET’s masked metadata and never include the plaintext token or invitation URL.
Stored events retain the payload captured when they were created. Event history, retries, and manual redelivery can therefore contain older payload shapes. Consult the Event catalog for the current shape of each event, including families without a matching public GET resource.