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: ABBYY
providerId: abbyy
generated: '2026-08-29'
method: searched
created: '2026-05-04'
modified: '2026-08-29'
source: >-
  https://docs.abbyy.com/vantage/developer/api-introduction ("Rate Limits & Best Practices", HTTP 200),
  https://docs.abbyy.com/flexi-capture/cloud/rest-api-errors (HTTP 200),
  https://docs.abbyy.com/api-reference/catalogrecords/adds-records-to-the-specified-catalog,
  and a full-corpus search of the ABBYY documentation for rate/throttle/429 terms via the ABBYY
  documentation MCP server. All probed 2026-08-29.
tags:
  - AI Automation
  - Document Processing
  - Rate Limiting
limit_count: 0
description: >-
  ABBYY publishes NO numeric rate limit for the Vantage APIs. The section of the developer docs headed
  "Rate Limits & Best Practices" contains no limit at all — it gives a batch ceiling, a polling cadence and
  a retry recommendation. No X-RateLimit-*, RateLimit-* or Retry-After header is declared in either
  OpenAPI document or documented anywhere, and neither spec declares a 429 response on any of its 36
  operations. A client has no runtime signal to back off on and no published number to design against.
headers: {}
response_codes: {}
limits: []
note: >-
  This file previously carried invented free/professional/enterprise quotas (10 rpm, 1,000/month, and so
  on) written by the 2026-05-04 bulk sweep. ABBYY publishes none of those numbers. They are removed.
published_constraints:
  - constraint: batch-size
    scope: per-request
    limit: 5000
    unit: catalog records
    operation: AddRecords
    source: https://docs.abbyy.com/vantage/developer/api-introduction
  - constraint: max-file-size
    scope: per-request
    limit: 30
    unit: MB
    note: Stated as the ceiling for the single-API-call processing pattern.
    source: https://docs.abbyy.com/vantage/developer/getting-started
  - constraint: polling-interval
    scope: client-guidance
    limit: 5-10
    unit: seconds
    note: Recommended interval when polling transaction status; not enforced.
    source: https://docs.abbyy.com/vantage/developer/api-introduction
  - constraint: file-name-uniqueness
    scope: per-transaction
    note: Duplicate file names within one transaction return 409 Conflict. A data constraint, not a rate limit.
other_surfaces:
  - api: ABBYY FlexiCapture Cloud for Invoices API
    throttled: true
    response_codes:
      throttled: 429
      service_unavailable: 503
    headers: {}
    limit_published: false
    backoff:
      strategy: exponential
      first_retry_seconds: 5
      max_wait_seconds: 60
    cause: >-
      ABBYY attributes 429 and 503 to workload spikes while Azure Resource Manager allocates additional
      processing capacity, rather than to a per-key quota.
    source: https://docs.abbyy.com/flexi-capture/cloud/rest-api-errors
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com