Pull the movements a connection can reach
From a signed-in screen, asks the bank for anything new first, with the caller’s own address as Ponto requires, then reads. From anywhere else, or for support reading a customer’s team, it only reads what Ponto already holds. A movement already on the account is left alone, so running this twice imports nothing the second time. An expired access token is refreshed here rather than reported. With bankAccountId, the account is read through whichever connection feeds it now. An account that turns out not to be readable any more is named in stopped rather than failing the others, and one the bank could not be asked about is named in unasked, showing what the bank had already reported; unaskable says the caller’s own address is one Ponto cannot be given, so nothing was asked for and checking again from there answers the same. New movements are then placed against what they pay where the owner has placement on; placed and waiting say how that went, and a placing that fails still answers with what was read, waiting null, for the hourly pass to finish.
Request
- Base URL: http://localhost:5180
- URL: http://localhost:5180/api/v1/banking/ponto/sync
- Auth: API key in cookie better-auth.session_token
Request body
Response
What came in.
Changes
No recorded changes to this operation across all 1 revision of this API.