Trendtrack
Trendtrack
DashboardGet API keyIntroducción
Primeros pasosAutenticaciónCréditos y facturaciónErroresLímites de tasaTime windowsSolución de problemas
Guías

Límites de tasa

Gestiona correctamente las respuestas 429 y utiliza Retry-After de forma segura.

Current behavior

Trendtrack owns authenticated public API rate limiting in the backend runtime. If a request is blocked, the API returns a canonical 429 rate_limited response.

Headers to watch

  • Retry-After tells you when to retry after a 429.
  • X-Request-Id helps correlate support or debugging investigations.

Implementation guidance

  • Back off and retry after the interval in Retry-After.
  • Treat rate limiting separately from billing failures such as insufficient_credits.
  • Use the raw OpenAPI and Swagger references to verify per-endpoint behavior as the surface evolves.

Errores

Aprende la estructura estable de errores y los códigos de error públicos más importantes.

Time windows

Pick the right current-ranking sort keys, historical time windows, snapshotDate, and freshness controls.

On this page

Current behaviorHeaders to watchImplementation guidance