Skip to main content

Overview

Data freshness varies by endpoint because each endpoint draws from a different upstream source. Every response includes a meta.as_of timestamp so you always know the age of the data you’re working with.

Freshness by endpoint

Understanding the timeline

Near real-time endpoints (Merchants, Gateway transactions) reflect changes within minutes. If you update a merchant in your CRM, the API will show the change shortly after. T+1 endpoints (Pricing, Transactions) are refreshed overnight. Data from Monday’s transactions appears in the API on Tuesday morning. Month-close endpoints (Statements, Residuals) depend on processor reporting cycles. Data for January typically becomes available in the first week of February.

Checking freshness in code

Residual report status

Residual report endpoints include a report_status field that indicates completeness: