What it is

Everything you can do in Austen, you can do from your own code. The developer API exposes the full pipeline over JSON and HTTPS: create a brief, generate a plan, produce the article, then publish or distribute it. Bring your own front end, wire Austen into an existing workflow, or schedule content from a backend job. The output is the same on-brand, search-ready article you get in the app.

Two ways to drive it

Choose the level of control you want.

Granular. You drive each transition yourself: create a brief, generate and edit the plan, approve it, then edit, publish, and distribute the article. This maps directly to the in-app workflow and gives you a checkpoint at every stage.
Auto-pilot. Hit one endpoint with a brief, or even just a topic, and Austen runs every stage through to a finished article. Ideal for volume and for hands-off scheduling.

Built for real integrations

The API is designed to sit in production systems, not just demos.

Signed webhooks notify your endpoint as briefs, plans, and articles change state, so you never have to poll blindly. Each delivery is signed and carries a delivery id for replay protection.
Idempotency keys make retries safe: the same key replays the original result instead of duplicating work.
Polling fallback is there when you cannot expose a webhook. Every async call returns a status URL to check.
Scoped tokens let you grant account-wide or single-project, read-only or read-write access.
Stable error codes make failures easy to handle in code.

How it fits the rest of Austen

The API drives the same pipeline as the app, so anything you create through it appears in your account: real briefs, structured plans, and articles, scored by SEO and GEO analysis. Your team can pick up any piece in the editor, and you can publish straight to WordPress or fire outbound webhooks to any destination.

Want your AI assistant to drive the pipeline in plain language instead? Use the MCP server, which is built on the same foundation.

Who it's for

Engineering teams adding content generation to an existing product or marketing stack. Agencies automating production across many clients. Anyone moving enough volume that clicking through the app by hand stops making sense. Full reference documentation, including authentication, endpoints, and webhook verification, is available inside your account.

Common questions

What format is it? JSON over HTTPS, with bearer-token authentication.

Do articles created over the API still get optimised? Yes. The API runs the same pipeline as the app, including SEO and GEO optimisation.

How do I get notified when an article is ready? Subscribe a webhook endpoint and Austen posts you a signed event, or poll the status URL returned by the call.

Where are the full docs? In your account, under Developer API. Sign in to read the complete reference.