generated: '2026-08-13'
method: searched
source: https://docs.talon.one/docs/dev/management-api/overview
specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Talon.One
providerId: talon-one
created: '2026-07-10'
modified: '2026-08-13'
reconciled: false
tags:
- Promotions
- Loyalty
- Coupons
- Rate Limiting
- Quotas
description: 'Talon.One publishes exactly one numeric API rate limit: every Management API endpoint is
  limited to three requests per second. That limit is stated in the Management API overview, which also
  says the Management API is for back-office operations and not for real-time integrations. The Integration
  API carries no published numeric cap — it is the high-load, real-time surface, sized by the customer
  contracted data volume and the capacity of that customer dedicated deployment. Bulk work is deliberately
  pushed off the synchronous path onto asynchronous endpoints (coupons_async, coupon deletion jobs, imports)
  and onto the no_total list variants.'
notes: Re-read on 2026-08-13. The previous revision of this file said no numeric limit was published anywhere;
  that was wrong — the Management API overview publishes three requests per second per endpoint. Use the
  asynchronous bulk endpoints for large coupon generation, deletion and imports, and the no_total list
  variants for large result sets. Load testing must be coordinated with Talon.One in advance (https://docs.talon.one/docs/dev/tutorials/load-test).
sources:
- https://docs.talon.one/docs/dev/management-api/overview
- https://docs.talon.one/docs/dev/integration-api/overview
- https://docs.talon.one/oas/management.yaml
responseCodes:
  throttled: 429
limits:
- name: Management API
  scope: per-endpoint
  window: 1 second
  limit: 3
  unit: requests
  published: true
  source: https://docs.talon.one/docs/dev/management-api/overview
  notes: 'Quoted from the provider docs: "Each of its endpoints has a limit of three requests per second."'
- name: Integration API
  scope: deployment
  window: null
  limit: null
  unit: requests
  published: false
  notes: No numeric limit published. Throughput is bound by the contracted data volume and dedicated deployment
    capacity; this is the surface Talon.One sizes for checkout-path traffic.
- name: Promotion data volume
  scope: account
  window: contract period
  limit: null
  unit: transactions/sessions
  published: false
  notes: Commercial ceiling rather than a request-rate limit; set by the package band. See plans/talon-one-plans-pricing.yml.
- name: Webhooks per account
  scope: account
  window: null
  limit: null
  published: false
  notes: Contractual maximum, shown in the Campaign Manager under Account > Usage & Limits.
policies:
- name: Asynchronous Bulk Operations
  description: Large coupon creation and imports are provided as asynchronous jobs (e.g. coupons_async)
    to keep synchronous request paths responsive.
- name: Pagination
  description: List endpoints offer no_total variants for cursor/offset pagination over large result sets
    to reduce load.
- name: Backoff Strategy
  description: Clients should implement exponential backoff with jitter and honor Retry-After on any 429
    responses.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
limit_count: 2
headers:
  published: false
  observed: []
  note: No rate-limit response headers are declared in any of the five published OpenAPI documents — no
    X-RateLimit-*, no RateLimit-*, no Retry-After — even though 429 is a declared response on 34 operations.
    An agent therefore cannot read remaining quota or a retry delay from the response and must back off
    blindly.