Inblog
Get started
← All updates
Improvement

A faster, more predictable inblog API

Post lists are lighter, but integrations that need content_html must request it explicitly. Pagination and rate-limit behavior are more predictable too.

The inblog API now returns lighter post lists and handles pagination more consistently.

Action required for some integrations: If an existing integration reads content_html from GET /v1/posts, add it to fields[posts]. List responses no longer include the field unless it is requested.

  • GET /v1/posts no longer includes content_html by default, reducing unnecessary response work. Request it when needed with fields[posts]=title,content_html; individual post responses still include the body.
  • JSON:API pagination with page[number] and page[size] now works alongside the existing page and limit parameters. Page size is capped at 100.
  • Read requests return clear rate-limit headers and a retry interval when a client needs to slow down.
  • Individual API routes and the first request examples in the guide have been corrected so copy-and-paste requests reach the intended endpoint.

See the updated API reference for request and response details.