Content API for any website

Pull articles into any stack

Next.js, Astro, Hugo, Rails, or a CMS you built yourself: if it can make an HTTPS request, it can fetch finished articles from Rankbox as clean HTML or Markdown.

Get your API key How setup works

Included with every plan · Free 7-day trial

GET/api/public/v1/articles?since=…Sample
Authorization: Bearer rv_live_••••••••

200 OK
{
  "articles": [{
    "id": "8f14e45f-…",
    "slug": "how-to-run-a-sprint-without-chaos",
    "title": "How to Run a Sprint Without Chaos",
    "description": "A sprint plan that survives Monday…",
    "body_html": "<h2>Plan the sprint in…",
    "body_markdown": "## Plan the sprint in…",
    "tags": ["sprints", "agile"],
    "seo_score": 94,
    "published_url": null
  }],
  "count": 1,
  "next_since": "2026-09-21T09:00:12Z"
}
endpoints, all JSON over HTTPS
3
every article in both formats
HTML + MD
articles per request, with a cursor
100
stack that can make an HTTPS request
Any
Rankbox for REST API

Everything a build step needs

Pull finished articles into any stack with one revocable key.

  1. 01

    Only what changed

    Pass since= and get only articles published or edited after your last sync. Save next_since and send it back next time.

  2. 02

    Ready to render

    Every article comes as HTML and as Markdown, with its slug, meta description, tags, and SEO score.

  3. 03

    Close the loop

    Report an article's live URL and Rankbox knows where it lives. The backlink exchange uses it to verify links placed on the page.

What every article includes

One JSON shape across every endpoint, so a single type covers your whole integration.

FieldWhat it holds
  • idStable identifier. Update by it, never duplicate.
  • slugURL-safe, ready for your routes
  • titleThe article headline
  • descriptionMeta description
  • body_htmlRendered HTML: headings, lists, and links
  • body_markdownThe same article as Markdown
  • tagsTopic tags, as an array
  • seo_scoreRankbox's SEO/GEO score, 0 to 100
  • published_urlThe live URL you reported, or null
  • updated_atThe last change. Drives since=
Setup

Connected in three steps

A few lines in your build step, in any language that can make an HTTPS request.

  1. 1

    Create a key

    In Rankbox, open Integrations, choose Any site, and create a key. It's shown once, so keep it with your other secrets.

  2. 2

    Fetch your articles

    Call GET /articles at build time or on a schedule. Your dashboard shows the site as Live from its first request.

  3. 3

    Report the live URL

    Once a page is up, PATCH /articles/{id} with its published_url. The URL must be on your own site.

Get your API key Included with every plan · Free 7-day trial
curl "https://rankbox.xyz/api/public/v1/articles?since=2026-01-01T00:00:00Z" \
  -H "Authorization: Bearer $RANKBOX_KEY"
  • GET/pingChecks a key and returns your brand name
  • GET/articlesFinished articles, oldest change first
  • GET/articles/{id}One finished article
  • PATCH/articles/{id}Report where it went live
Rankbox · IntegrationsSample

Your site is connected

Last synced 4 min ago. Every published article has reached it.

Last sync

4 min ago

Delivered

28 of 28

published

On the way

0

all caught up

Plannora · API

Live

rv_live_a1b2c3…

Synced 4 min ago

Up to date

Delivery status

Know it's working, not just connected

A key existing proves nothing. Rankbox watches for your site's requests and shows exactly which articles have arrived.

  • Live. Your site asked for articles in the last 48 hours. Everything is flowing.

  • Waiting. The key is ready and Rankbox is listening. It turns Live the moment your site first calls in.

  • Idle. No request for 48 hours. Rankbox flags it, so articles never quietly stop arriving.

Security

Your site holds the key

Every connection runs on one key per site. Here's everything that key can and can't do.

Limited by design

A key can fetch your finished articles and report where they went live, on your own domain. Nothing else in your account.

No passwords shared

Rankbox never logs into your site. Your site pulls articles in with a key you can see, replace, and revoke.

Stored as a hash

A key is shown once. Rankbox keeps only its SHA-256 hash, so a database leak never exposes a usable key.

Revoke in one click

Replace a key that may have leaked, or revoke one you no longer use. Syncing with it stops the moment you do.

Read how we handle security
FAQ

REST API questions

Everything you need to know about connecting Rankbox with the REST API.

Whatever fits your build. You only get what changed since your last call, so hourly or daily is plenty. Rankbox marks a site Idle after 48 hours without a request.

Fetch your finished articles and report where each one went live, on your own domain. It can't read or change anything else in your account.

No. Only finished articles are returned. Drafts stay in Rankbox until you finish them.

Requests with it fail straight away. Create a new key, swap it in, and your site picks up from its saved since= cursor.

Keys work while your account has an active trial or plan. If a plan lapses, requests return an error until it's active again, and your dashboard says syncing is paused.

Questions about pricing or plans? See pricing

More integrations

Publishing somewhere else too?

Every integration runs on the same engine and the same kind of key.

See all integrations

Start pulling articles today

Create a key, make one request, and your site has every finished article in HTML and Markdown.

Get your API key

Included with every plan · Free 7-day trial