Export Data API - Individual: rate limits, quotas, and concurrency

Modified on Tue, 17 Nov at 5:13 PM

This article answers common questions about limits when using Schema App’s Individual Export Data API (the data CDN at data.schemaapp.com) for custom or server-side deployments. For how to build request URLs, headers, and encoding, see Export Data API - Individual.

Short answers

  • Monthly quotas: Schema App does not apply a published per-account monthly request quota on Individual CDN lookups.
  • Per-account rate or concurrency limits: There is no separate product “requests per second” or concurrent-connection limit billed or enforced per Schema App account for this CDN path.
  • Shared edge protection: Like most public CDNs, traffic is protected by AWS CloudFront and WAF rules that can temporarily block abusive traffic from a single source IP. This is anti-abuse protection for the shared platform, not a customer plan quota.
  • Practical guidance: For page-by-page SSR or edge injection, normal production traffic patterns are expected. For downloading large portions of an account’s markup at once, use the Bulk Export Data API instead of issuing thousands of Individual CDN GETs in a short window from one IP.

What the Individual API is

Each request asks for cached JSON-LD for one page URL (Base64-encoded in the path). Responses are served from Schema App’s markup CDN (CloudFront in front of object storage). Responses include standard cache headers so intermediaries and clients can reuse markup for a period of time (commonly on the order of days; see cache-control / Cache-Control on the response).

Recommended patterns for custom deployments

  1. Edge or origin SSR: Prefer Schema App’s Cloudflare Worker or Akamai EdgeWorker integrations when available, so markup is injected once per HTML response at the edge rather than every browser calling the CDN directly.
  2. Server-side fetch: If your application fetches Individual URLs itself, reuse responses (respect cache headers), strip query strings/fragments before encoding (as documented), and avoid opening unbounded parallel floods from a single NAT IP.
  3. Bulk / warehouse use cases: Use Bulk Export (api.schemaapp.com/export) with paging or the download option when you need many pages at once.

If you see HTTP 403 / blocked responses under heavy load

Sudden blocks under very high request volume from one IP may indicate edge flood protection. Spread load across time, reduce concurrency, cache aggressively, or switch bulk pulls to the Bulk Export API. Contact Schema App Support with approximate request rate, source IP range, timestamps, and response codes if you need help reviewing a block.

Related articles

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article