---
title: "Sync Account"
method: POST
path: "/v1/accounts/{account_id}/sync"
---

# Sync Account

`POST /v1/accounts/{account_id}/sync`

## Request

- Base URL: `https://api.quantradin.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.quantradin.com/v1/accounts/{account_id}/sync`
- Auth: none declared

Re-run the forward-walk for every RUNNING deployment on this account
(advances marks / closes matured positions).  Runs in the background;
returns immediately with {status: 'syncing'}.

LEGACY route: it authenticates with the single per-desk KEY (X-Vega-Key).
Coders on the newer account KEY PAIR (X-Vega-Account-Key-Id +
X-Vega-Account-Secret) reach for a "sync" step that doesn't exist for the
pair — deploying already kicks the first forward-walk. When we see the
pair here, say that in plain words instead of a bare 401 (auth behavior
is unchanged — this path still refuses; only the message is kinder).

## Path parameters

- `account_id` integer, required

## Headers

- `x-vega-key` string, nullable
- `x-vega-account-key-id` string, nullable
- `x-vega-account-secret` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/quantradin/apis/vega-api.md) · [All operations](https://skmtc.dev/quantradin/apis/vega-api/llms.txt) · [OpenAPI document](https://skmtc.dev/quantradin/apis/vega-api/revisions/47add154ef38?raw)