Skip to content
TAM Reporting

Quotas and limits

Rate limits and rolling 24-hour run quotas for TAM Reporting.

Two independent controls apply: per-endpoint rate limits and a rolling 24-hour run quota.

Rate limits

EndpointLimit
POST /api/reports/:id/run1 call / 30 seconds
POST /api/reports/run1 call / 30 seconds
All other reporting endpoints1 call / 5 seconds

Limits apply at seat level. Two tokens on the same seat share the same limit.

Run quota

You can run 75 reports in a rolling 24-hour window by default. After that, you cannot start more runs until slots free up. Creating or editing saved reports in TAM does not consume quota; running them does.

Contact your Teads account representative if you need a higher quota.

Affected routes:

  • POST /api/reports/run
  • POST /api/reports/:id/run

Check usage before bursting:

GET /api/reports/quotas
Authorization: YOUR_API_KEY
FieldMeaning
usedRuns in the past 24 hours
totalAllowed runs per 24 hours
next_available_slotEpoch milliseconds when the next run is allowed

A 429 on a run endpoint means the quota (or the 30-second rate limit) was hit. The one-time-report error body can look like:

{
  "error": {
    "message": "Error message",
    "details": []
  }
}

Possible messages include required parameters missing, and User X reached its Api quota CURRENT_QUOTAS / TOTAL.

Date and data availability

ConstraintDetail
Earliest dataJanuary 2020
Maximum period1 year
Geo dimensions (country_*, region_*, …)From 1 April 2024
Cookieless Delivery dimension (TAM UI)From 12 May 2023

Unique Viewers

uv_impression is only valid with a fixed set of dimensions and metrics. See Unique Viewers.