Refresh User accounts

Triggers an asynchronous job to refresh open banking data for all accounts a user has connected through the direct connection journey.

If at least one account qualifies for refresh, the service responds with 201 Created, including a new jobId and per-account results in metadata. If no work is performed—for example, because all accounts are skipped—the service responds with 200 OK, sets status to SKIPPED, and does not return a jobId.

Accounts will be skipped if they've already been refreshed recently (RATE_LIMITED), or if we no longer have consent to refresh that account (ACCOUNT_EXPIRED).

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

The User ID

Responses

401

API key authentication unsuccessful.

404

The userId does not exist for this partner.

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