Data Freshness

Turnqey uses cached data and controlled refreshes to protect source platforms, reduce latency, and avoid unnecessary API calls.

GET /v1/api/account/{accountId}/balances may return cached data.

To request a refresh, use:

forceRefresh=true

Example:

GET /v1/api/account/{accountId}/balances?forceRefresh=true

When forceRefresh=true, Turnqey attempts to refresh source data if the account data is eligible for refresh. If the data is already fresh, Turnqey may return the latest cached result.

GET /v1/api/account/{accountId}/transactions follows the same pattern.

Example:

GET /v1/api/account/{accountId}/transactions?forceRefresh=true

Initial syncs can take longer than cached reads. Partner applications should show a clear syncing state while Turnqey processes the account.

Show users:

• Last updated timestamp
• Source connection status
• Syncing state during initial processing
• Reconnect-required state when authorization expires
• Whether balances are source-reported or calculated from transaction history

Do not force refresh on every page load.

Use cached data for normal views. Reserve forced refreshes for:

• Explicit user refresh actions
• Scheduled sync jobs
• Stale data checks
• Support investigations

For integration support, contact:

• support@turnqey.xyz