Teads Developer Portal

Rate limits

The rate limit applies to all routes. When a request is rejected, the API returns HTTP 429 and a Retry-After header containing the number of seconds to wait. The interval between reports can be as long as 30 minutes.

Only two reports may be running concurrently. When that limit is reached, the API returns:

REPORTING.ERROR.RUNNING_REPORT_QUOTA_REACHED

Wait for an existing report to finish, check active reports with List processing reports, or cancel one with Cancel a report.

Generation quota

The API allows at most 50 generated reports in a rolling 24-hour window. When the quota is exceeded, the API returns:

REPORTING.ERROR.PAST_24H_REPORT_QUOTA_REACHED

Date range limits

Condition	Error
Report includes data before 2020	`REPORTING.ERROR.PERIOD_NOT_FULLY_AVAILABLE_IN_NEW_REPORTING_ENGINE`
Report period is longer than one year	`REPORTING.ERROR.REPORT_PERIOD_TOO_LONG`
`uv` is used for a period longer than 100 days without `day`	`REPORTING.ERROR.UV_REPORT_PERIOD_TOO_LONG`

Validation errors

Invalid request fields return HTTP 400. The legacy API can identify nested fields in the response:

{
  "obj.dimensions.dimensions.filters.insertions[0]": [
    {
      "msg": "error.expected.jsnumber",
      "args": []
    }
  ]
}

Report failures

An accepted report can still finish with status: "error". Inspect the response message for details. A report with valid: false should not be polled as a successful report; correct the request and submit it again.

Deprecations

The source documentation marks these features as deprecated:

uv flag, deprecated starting January 1, 2024.
Expanded teads_billing and income finance metrics, deprecated starting January 1, 2024.
Legacy metrics including callJS, slot_available, noSlot-DOM, noSlot-MinSlot, passback, errorVast, and vastError are being phased out in favor of the newer names documented on the metrics page.

Support

For API support, contact api@teads.tv.

Limits and errors