SEO for SaaS
Start
API reference

Errors and limits

Status codes, the error body, and rate limits.

Errors share one body:

json
{  "success": false,  "error": { "code": "NOT_FOUND", "message": "Article not found.", "path": "/api/v1/…", "timestamp": "…" },  "meta": { "requestId": "…" }}

Branch on error.code, and include meta.requestId when you contact support.

StatuscodeWhen
401UNAUTHORIZEDMissing, unknown, or revoked content key.
403FORBIDDENA content key used on another project, for a write, or on any endpoint other than reading articles.
404NOT_FOUNDNo published article at that slug or ID. A draft reads as missing.
429RATE_LIMIT_EXCEEDEDMore than 300 requests in a minute on one key from one edge location. Wait, then retry.

Limits

  • 300 requests a minute per content key, counted per edge location (requests from different regions are counted separately).

  • 100 articles per page.

  • Published articles only.

A static build reads each article once per build, and a revalidating site once per refresh, so a normal site stays far below the limit. If your build reads a large site in parallel, cap the number of parallel requests.

Featured on

The launch sites and tool directories that list SEO for SaaS.

Also listed on SeeWhatNewAI, AiToolGo, What Is Ai Tools and MeoAI.