autoranko

Feed · REST API · Webhook

Publish to any website: feeds, API or a webhook

No connector for your platform? Three methods cover everything else: pull articles from RSS/JSON feeds, fetch them with the REST API, or have Autoranko push each article to your own endpoint as signed JSON.

  • About 30 minutes to connect (estimate)
  • Last verified November 8, 2026

How it connects

Feeds are the simplest. Every site gets private RSS 2.0 and JSON Feed URLs with its published articles, which any importer, static-site build or automation tool can read. They suit sites that rebuild on a schedule and don’t need drafts or updates.

The REST API gives your code full control. Create article jobs, follow them with webhooks or polling, read the finished article — title, meta description, HTML — and publish it however your stack works. Everything is described by one OpenAPI 3.1 file, with samples in cURL, Node.js, Python and PHP.

The publishing webhook turns any site into a push target. Autoranko sends each published or updated article to your HTTPS endpoint as JSON — HTML without the H1, meta description, images, FAQ and JSON-LD — signed with HMAC-SHA256 and a timestamp. Your endpoint stores it and replies with the article’s public URL. If your site was built with Lovable, Cursor, Claude Code, Bolt or v0, the dashboard has a ready-made prompt that asks your coding tool to build that endpoint.

Set up any site

  1. 1

    Create a custom site

    In Dashboard → Integrations, add a non-WordPress site with your domain and choose Custom (feed/API). This gives the site its feed URLs and makes it available to the API.

  2. 2

    Pick your method

    Choose feeds if your site can import them, the API if you’d rather write the integration yourself, or the publishing webhook if you want articles pushed to you as they’re published.

  3. 3

    For the API, create a token

    In Dashboard → API, create a token (ar_live_…) and keep it on your server. List your sites with GET /sites to find the site ID, then create jobs for it.

  4. 4

    For the webhook, build and register the endpoint

    Build an HTTPS endpoint that verifies the signature, stores the article under its ID and replies with the article’s public URL. Register it with its secret, send the test event, then publish a real article.

  5. 5

    Review generated code before going live

    If an AI coding tool built your endpoint from the installation prompt, read the code first: check the constant-time signature comparison, that updates edit the existing article instead of creating a new one, and that each page renders a title, a meta description and a canonical URL.

What gets published

Exactly what Autoranko sends and controls on this platform, as of the last verification date.

Capabilities of the Any site integration
CapabilityPublishing webhookFeeds (RSS/JSON)REST API
TitleSupportedSupportedSupported
Article body (HTML)SupportedSupportedSupported
Meta descriptionSupportedSupported1Supported
Featured imageSupportedPartly2Partly3
Images in the articleSupported4Supported4Supported4
Publish as a draftPartly5Not supported6Partly7
Update a published articleSupported8Partly9Partly7
UnpublishSupported10Not supported6Partly7
Tags or categoriesNot supportedNot supportedNot supported
JSON-LD structured dataSupported11Not supportedNot supported
SupportedPartlyNot supported
  1. 1.The feed item’s description.
  2. 2.Inside the article HTML; the feed has no separate image element.
  3. 3.Inside the article HTML returned by the API.
  4. 4.Images inside the article body may be served from autoranko.com/media when the platform can’t store them; they’re deleted 30 days after you remove the site.
  5. 5.Your endpoint decides whether an article goes live.
  6. 6.Feeds only contain published articles.
  7. 7.Your code fetches the article and decides what to publish.
  8. 8.Sent as an article.updated event with the same article ID.
  9. 9.The feed always carries the current text; whether your importer re-syncs it depends on the importer.
  10. 10.Sent as an article.unpublished event with the same article ID; your endpoint takes the page down.
  11. 11.Sent in the json_ld field for your pages to render.

Limits and honest caveats

Feeds can’t carry drafts or unpublishing, and the API leaves publishing entirely to your code. The publishing webhook sends published and updated articles but has no unpublish event yet, so take an article down on your side. No method sends tags.

Images are linked from autoranko.com/media unless your endpoint downloads them, and they stop loading 30 days after you remove the site from Autoranko — download them if you want to keep them. Every method uses the same article allowance as any other platform.

Troubleshooting

The messages below are exactly what Autoranko shows in the dashboard or returns from the API, with what they mean and how to fix them.

invalid_token
The API answered 401 invalid_token: the token is malformed, revoked or belongs to another account. Create a new token in Dashboard → API and send it as Authorization: Bearer ar_live_…
plan_limit
The API answered 429 plan_limit: the account has used its article allowance for the period. Waiting a few seconds won’t help; upgrade the plan or wait for the allowance to reset.
Publishing failed: …
Your webhook endpoint answered with an error, timed out or didn’t return a URL. The article stays in review with the reason. Fix the endpoint and publish again — the article ID stays the same, so a retry doesn’t create a duplicate.
Signatures never match
Verify the signature over the raw request body, byte for byte, before parsing the JSON; re-serialized JSON has different bytes. Use the whole secret, prefix included, and a constant-time comparison.

Questions

Which method should I choose?+
Feeds if your platform has an importer and published-only articles are enough; the publishing webhook if you can run a small endpoint and want updates pushed to you; the API if you want your own code to decide everything.
Can I use Zapier, Make or n8n?+
Yes. They can read the RSS or JSON feed, call the REST API with your token or receive webhooks — then post the article to any platform they support.
Do I need a developer?+
For feeds, usually not. For the API or the publishing webhook, someone has to write or review a little code. The installation prompt can draft the endpoint with an AI coding tool, but read what it generates before relying on it.

Connect your site in minutes

Start on the free plan — no card — and publish your first article to your own platform.