Refresh Transactions When You Need Them
Manual transaction refresh lets you request newer banking transaction data when your product needs it, alongside Fiskil’s ongoing background updates.
Trigger one additional refresh job per end user per day. Each job syncs new transactions across the accounts and consents associated with that end user.
Refresh at the moments that matter
Refresh before an account review, an accounting close or a lending reassessment, then update your product when the sync completes.
Request, then follow the result
Call POST /v1/banking/transactions/refresh with the end_user_id. The job runs asynchronously: banking.transactions.sync.completed signals success, while banking.transactions.sync.failed signals failure. Read the webhook guide
Developer Notes3
- One additional banking transaction refresh job per end user per day.
- Use the completion webhook to fetch the refreshed data.
- Handle rate limits and failures as described in the API documentation.
