Skip to content
Developers
GuidesAPI reference
slimwiki.comGet an API key

Guides

  • Quickstart
  • Authentication
  • Errors
  • Pagination
  • Rate limits
  • Content format
  • Versioning

Tools and agents

  • CLI
  • MCP server
  • Agent skill

API reference

  • Overview

Users

  • Retrieve the key ownerget

Accounts

  • List accountsget

Wikis

  • List wikisget
  • Retrieve a wikiget

Pages

  • List pages in a wikiget
  • Search pages in a wikiget
  • Find a page by slug or hashget
  • Create a pagepost
  • Retrieve a pageget
  • Delete a pagedelete
  • Archive a pagepost
  • Restore a pagepost

Guides

Rate limits

Each API key can make 120 requests per minute. Response headers tell you how much of that is left.

On this page

  • The limit
  • Rate limit headers
  • When you go over the limit
  • Backing off

The limit

The limit is 120 requests per minute, counted per API key. Two keys do not share a count, and every request made with a key counts towards that key's limit.

Rate limit headers

Rate limit response headers
HeaderMeaning
X-RateLimit-LimitThe number of requests the key may make in one window.
X-RateLimit-RemainingThe number of requests left in the current window.
X-RateLimit-ResetThe number of seconds until the current window ends and the count starts again.
Retry-AfterOnly on a 429 response: the number of seconds to wait before trying again.

When you go over the limit

A request over the limit is not carried out. It gets a 429 response with the code rate_limited and a Retry-After header.

Response headers
HTTP/1.1 429 Too Many Requests
Retry-After: 12
X-RateLimit-Limit: 120
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 12
Response · 429
{
  "error": {
    "code": "rate_limited",
    "message": "Too many requests. Slow down and try again.",
    "request_id": "2f9d6c1e-7a4b-4d3c-8e5f-1a2b3c4d5e6f"
  }
}

Backing off

  • On a 429, wait for the number of seconds in Retry-After, then send the request again.
  • If the retry is also rate limited, wait longer before each further attempt instead of retrying at once.
  • Watch X-RateLimit-Remaining and slow down before it reaches zero, rather than sending requests in bursts.
  • When you read many pages, use a larger page_size so you need fewer requests. See Pagination.

Previous

Pagination
The shape of list responses and how to page through pages and search results.

Next

Content format
How a page body is represented: nodes, text and marks, with a full example.

SlimWiki Developers

slimwiki.com