Trigger bank transaction webhooks

Manually triggers webhook delivery for specified bank transactions. This can be used to re-emit webhooks that may have been missed or to force re-matching of transactions.

You can specify which webhook event types to emit: banktransaction.created for transaction data or transaction.match.created for match results.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
uuid
required
Body Params

Webhook trigger request

ids
array of uuids
required
length ≥ 1

List of bank transaction identifiers to emit webhooks for. Must contain at least one ID.

ids*
webhooks
array of strings

The types of webhook events to emit.

webhooks
Allowed:
boolean
Defaults to false

Set to true to re-run the matching algorithm for the named transactions before emitting webhooks. Transactions that already have a match are genuinely re-scored: the existing match id is preserved when the pairing survives, updated when a better pairing exists, and removed when the movement no longer matches.

boolean
Defaults to false

After the re-match, emit the standalone bank-only feed entry for each named transaction the matcher left unmatched (idempotent per transaction — already-emitted standalones are skipped). Requires forceRematch: true and webhooks to include transaction.match.created; the request is rejected with 400 otherwise, because only a same-run re-match can distinguish a genuinely unmatched movement from a duplicate of an already-settled purchase.

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
OAuth2
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json