Re-pull normalized reference data

Re-pulls the requested reference collections (default: all) from the partner and upserts them into their normalized mirrors. Synchronous today — the response's AsyncOperation is already terminal (Completed/PartiallyCompleted/Failed) by the time it's returned; a collection that fails to pull does not block the others.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
length between 22 and 22
^[A-Za-z0-9_.]{22}$

Unique identifier of an AccountingConnection. A 22-character id.

Body Params
collections
array of strings
required

Which normalized reference collections to re-pull.

collections*
Allowed:
Headers
string
^(?:[A-Za-z0-9_.]{22}|[a-f0-9]{24})$

Select the Account for an Account-scoped operation. A direct ServiceAccount API key MUST supply this header, and the target must be within the ServiceAccount owner's or Authorization grant's Account boundary. A Person bearer may select an Account on which it has an active Stakeholder, and an Account session may select its bound Account (or a descendant only when the session explicitly includes descendants).

string
length between 1 and 255
^[\x21-\x7e]{1,255}$

Optional idempotency token for authenticated POST and PATCH requests. Reusing the same key and body returns the cached response for 24 hours, except credential operations that explicitly document a 409 because one-time secret material is never cached; reusing it with a different body returns 409 IdempotencyKeyConflict. Use 1-255 printable ASCII characters.

string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

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