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: Sync API
providerId: sync-api
created: '2026-05-04'
modified: '2026-08-12'
generated: '2026-08-12'
method: searched
source: https://sync-api.com/ (full site read 2026-08-12)
tags:
  - Advertising
  - Digital Marketing
  - In-App Advertising
  - Mobile
  - Programmatic
  - Real-Time Bidding
  - User Acquisition
  - Rate Limiting
  - Quotas
  - Throttling
description: >-
  Measured rate-limit record for Sync API. Sync API documents NO rate limits, and
  publishes no developer documentation in which limits could appear. This file
  supersedes a 2026-05-04 bulk-sweep scaffold that carried invented per-tier
  limits (10/100/1000 rpm) and an invented X-RateLimit-* header contract; none of
  those were ever published or observed, and they have been removed.
limit_count: 0
limits: []
headers: {}
responseCodes: {}
findings:
  - url: https://sync-api.com/
    status: 200
    finding: >-
      The public site is five pages (Home, About Us, Our Services, Partnerships,
      Contact Us) of marketing copy. There is no developer portal, API reference,
      or terms page that states a request quota, burst allowance, throttle window,
      or 429 behaviour.
  - url: https://sync-api.com/docs
    status: 404
    finding: No documentation surface exists on which limits could be published.
  - url: https://api.sync-api.com
    status: 0
    finding: >-
      NXDOMAIN across 8.8.8.8, 1.1.1.1 and 9.9.9.9. No live response could be
      observed, so no rate-limit response headers could be probed either.
notes:
  - >-
    Because the API host does not resolve, limits could not be established by
    observation as well as not by documentation. Both routes are closed.
  - >-
    No RateLimits pointer is emitted in apis.yml — a pointer asserts the provider
    publishes limits, and the measured answer is zero.