[
/docs
·
Connect
]
Consent scopes and expiry
How scopes, expiry dates and re-authentication fit together.
group
Connect
Each connection carries the scopes the user approved and an expires_at date. From v3.2.0, each scope can also have its own expiry when the bank sets different periods.
Seven days before a scope lapses, Sluice sends connection.expiring. Create a connect session with the same connection_id and send the user its link; they confirm the same scopes and the connection keeps its id.
If consent lapses before renewal, the connection moves to expired. Your stored data stays where it is, but no new syncs happen until the user renews.
[ 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