---
title: "Sync transactions for a connection"
method: POST
path: "/authorizations/{authorizationId}/transactions/sync"
tags: ["Connections"]
---

# Sync transactions for a connection

`POST /authorizations/{authorizationId}/transactions/sync`

Trigger a transactions sync for all accounts under this connection. Updates will be queued asynchronously. Transactions are not updated intra-day, but calling this endpoint can ensure that the previous day's transactions have been synced. For more information on sync behaviour, see: https://docs.snaptrade.com/docs/syncing

## Path parameters

- `authorizationId` string, uuid, required — Unique identifier for the connection (brokerage_authorization_id). This is the UUID used to reference the connection in SnapTrade.

## Query parameters

- `userId` string, required — SnapTrade User ID. This is chosen by the API partner and can be any string that is a) unique to the user, and b) immutable for the user. It is recommended to NOT use email addresses for this property because they are usually not immutable.
- `userSecret` string, required — SnapTrade User Secret. This is a randomly generated string and should be stored securely. If compromised, please rotate it via the [rotate user secret endpoint](/reference/Authentication/Authentication_resetSnapTradeUserSecret).

## Response `200`

OK

- BrokerageAuthorizationTransactionsSyncConfirmation — Confirmation that the transaction syncs have been scheduled.
  - `detail` string — Transactions sync confirmation details

## Other responses

- `401` — Unauthorized, invalid credentials for this resource
- `402` — Unable to sync with brokerage account because the connection is disabled.

---

[API](https://skmtc.net/passiv/apis/snaptrade.md) · [All operations](https://skmtc.net/passiv/apis/snaptrade/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/passiv/snaptrade/versions/993e058b557e/schema)