Sync bank key

Enqueues a background job that re-fetches the bank accounts exposed by this
credential and refreshes their capability data. Use it to repopulate stale
account/permission information without deleting and recreating the key.

The job runs asynchronously — this endpoint only acknowledges the enqueue and
responds 202 Accepted. Requests are debounced: if a sync was already enqueued
for this key within the last 30 seconds, the request is a no-op and the
response carries enqueued: false (still 202). This protects the upstream
bank from rapid retries.

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

The id of the bank key

Headers
uuid
required

UUID of the company on whose behalf the request is made. Send it on banking
requests to identify the acting company. Note that user-scoped list endpoints
(e.g. the recipients/transactions indexes) resolve results across all companies
the authenticated user is a member of, rather than strictly from this header.
See The company-id header for details on how to obtain
a value for this header and the error responses to expect when it is missing or invalid.

Responses

401

Unauthorized

404

Bank key not found

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