Skip to content

reblogger.ai developer platform

Build with reblogger.ai

One request turns any URL or topic into a publish-ready, SEO-optimized article — with title, meta description, FAQ, images and clean HTML, Markdown or Gutenberg blocks.

Overview

The reblogger.ai API is a JSON REST API at https://reblogger.ai/api/v1. You send a source — a URL to rewrite or a topic to write about — and reblogger researches, outlines, writes and optimizes a complete article in the background. Generation is asynchronous: you get a generation id immediately and the article is usually ready within one to three minutes.

There are three ways to integrate:

  • REST API — for your own apps, CMS pipelines and automations (Zapier, Make, n8n).
  • MCP server — let AI assistants like Claude or Cursor write articles for you. See MCP server.
  • WordPress plugin — one-click connect, publishes native Gutenberg posts. See WordPress plugin.

Quickstart

Create an API key in the dashboard under Settings → API keys. The key starts with rb_live_ and is shown only once. Export it so the examples below can use it:

Shell
export REBLOGGER_API_KEY="rb_live_…"

1. Create an article

POST /articles reserves the credits and queues the generation. The response is 202 Accepted with the generation and the id of the article that will be filled in.

curl https://reblogger.ai/api/v1/articles \
  -H "Authorization: Bearer $REBLOGGER_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "source": { "type": "topic", "topic": "Balcony vegetable gardening for beginners" },
    "language": "en",
    "length": "medium",
    "tone": "friendly"
  }'
202 Accepted
{
  "generation": {
    "id": "cmh1x0gen7f2k0001",
    "object": "generation",
    "status": "queued",
    "stage": "queued",
    "progress": 0,
    "article_id": "cmh1x0art9q3m0001",
    "model": "claude-sonnet-5.5",
    "credits_charged": 1,
    "source": "api",
    "error": null,
    "created_at": "2026-10-31T09:24:11.000Z",
    "started_at": null,
    "finished_at": null
  },
  "article_id": "cmh1x0art9q3m0001",
  "links": {
    "self": "https://reblogger.ai/api/v1/generations/cmh1x0gen7f2k0001",
    "events": "https://reblogger.ai/api/v1/generations/cmh1x0gen7f2k0001/events",
    "article": "https://reblogger.ai/api/v1/articles/cmh1x0art9q3m0001"
  }
}

2. Wait for the generation

Poll GET /generations/{id} every few seconds until status is succeeded. For live progress (outline, streaming sections) use the event stream; to avoid polling entirely, register a webhook.

curl https://reblogger.ai/api/v1/generations/$GENERATION_ID \
  -H "Authorization: Bearer $REBLOGGER_API_KEY"

3. Fetch the article

curl "https://reblogger.ai/api/v1/articles/$ARTICLE_ID" \
  -H "Authorization: Bearer $REBLOGGER_API_KEY"

Publishing to WordPress?

Add ?include=blocks to get content_blocks — the body as native Gutenberg block markup, ready for post_content.

Conventions

  • Requests and responses are JSON with snake_case fields. Timestamps are ISO 8601 in UTC.
  • Errors use RFC 9457 application/problem+json with a stable title code — see Errors & rate limits.
  • Every response includes X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset.
  • Lists are cursor-paginated: pass starting_after with the previous page's next_cursor.
  • The machine-readable spec lives at /api/v1/openapi.json (OpenAPI 3.1) — import it into Postman, Insomnia or a client generator.

Where to next