[
/docs
·
Data
]
Syncing transactions
Page through history once, then read only what changed.
group
Data
The first sync downloads the history the bank allows, usually 12 to 24 months. Sluice sends transactions.available after the first page and again as each page lands.
Call GET /v3/transactions/sync with the cursor from your last call. The response holds three lists: added, modified and removed. Store the new cursor and you will never read the same change twice.
Pending transactions keep their id when they settle. When a bank changes the id anyway, Sluice matches the lines and sends a removed entry for the old one.
Set the sync schedule per connection: every 6 hours by default, down to every hour on paid plans.
[ example request ]
Node
Python
cURL
connect
import { Sluice } from ‘@sluice/node’;
const sluice = new Sluice(process.env.SLUICE_KEY);
const session = await sluice.connect.sessions.create({
user: ‘user_31c’,
scopes: [‘balances’, ‘transactions’],
});
// send session.url to your user
201 Created · 84 ms
id cs_7Hq2
url https://connect.sluice.dev/cs_7Hq2
expires_in 900
[
→
·
more guides
]
Next on the list.
Sluice® Template
$129 · one-time
NOVA STUDIO
/ SECURED BY POLAR