Skip to content
For developers

Your content workflow.
Connected to your tools.

Create posts, generate drafts, manage assets, and schedule content through one API. Use it with your own app or the automation tools you already know.

curl https://api.krevaya.com/v1/posts \
  -H "Authorization: Bearer krv_..." \
  -H "Content-Type: application/json" \
  -d '{
    "platform": "instagram",
    "body": "Unpopular opinion: the best travel days are the ones you didn't plan.",
    "schedule_at": "2026-08-21T18:42:00Z"
  }'

# 201 { "id": 627, "status": "scheduled", ... }

Everything your workflow needs.

Posts & scheduling

Create a draft for review or set a future publishing time. Your existing publishing rules still apply.

Writing & design

Generate drafts in your voice, upload assets, and apply your studio templates.

REST, GraphQL & MCP

Use the REST API, the GraphQL beta, or the hosted MCP server with the same scoped keys.

Events & webhooks

Receive HMAC-signed events when posts publish or fail, with retries for missed deliveries.

Start with a scoped key.

01

Create your key

Open Settings → API keys. Choose read, publish, generate, media or engage scopes — engage (replying to comments and DMs as you) is off unless you tick it. Your key is shown once and can be revoked at any time.

02

Make a request

Send your key in the Authorization: Bearer header or X-API-Key header. The same credentials work across REST, GraphQL, and MCP.

03

Connect your workflow

Create drafts, schedule posts, and register webhooks to keep your other tools up to date.

A few developer questions.

What can I build with the API?

Anything that creates, schedules, or reads content: pipe your blog into platform-native drafts, auto-schedule from your own tooling, wire n8n / Make / Zapier HTTP nodes to your queue, or feed results into your own dashboards. Posts, generation, assets, design, and webhooks are all covered.

How do I get a key?

Mint one in Settings → API keys inside the dashboard. Keys are scoped (read, publish, generate, media, engage), shown once, and revocable in one click. Send them as `Authorization: Bearer krv_...` or `X-API-Key`.

Can the API bypass my review queue?

No — and that's the point. API-submitted copy passes the exact same safety screening, plan caps, and review rules as everything else. Omit `schedule_at` and the post lands as a draft waiting for your approval; send a future timestamp and it schedules directly.

Is GraphQL production-ready?

GraphQL is in beta: `me`, `posts` and `createPost` mirror the REST surface today, authenticated with the same keys, and the graph grows from there. REST /v1 is the stable, full-coverage surface.

Which plans include API access?

API & MCP access is included from the Plus plan up — no separate developer tier, no extra metering surprise.

Bring your own workflow.

API and MCP access are included from the Plus plan up.

Join the waitlist