Build any automation
for social.
One API for your whole content pipeline. Connect Krevaya to n8n, Make, your agents, or something entirely new — every call runs through the same review-first guardrails as the dashboard.
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", ... }POST https://api.krevaya.com/graphql
mutation {
createPost(input: {
platform: "instagram"
body: "Unpopular opinion: the best travel days are the ones you didn't plan."
}) {
id
status # "draft" — waits in your review queue
}
}import requests
r = requests.post(
"https://api.krevaya.com/v1/generate",
headers={"Authorization": "Bearer krv_..."},
json={"topic": "no-itinerary travel", "platform": "threads"},
)
job = r.json() # drafts land in your review queue when doneconst r = await fetch("https://api.krevaya.com/v1/posts", {
method: "POST",
headers: {
Authorization: "Bearer krv_...",
"Content-Type": "application/json",
},
body: JSON.stringify({
platform: "facebook",
body: "Shipped: our new onboarding, rebuilt as a 90-second story.",
}),
});
const post = await r.json(); // { id, status: "draft", ... }Zero to first post in four steps
Settings → API keys. Scopes are read, publish, generate, media — shown once, revoked in one click.
Send Authorization: Bearer krv_... (or X-API-Key) on every request. Same keys work for REST, GraphQL and MCP.
Create posts and drafts, kick off generation in your voice, ingest assets, apply design templates — the whole pipeline is callable.
Register HMAC-signed webhooks with retries for post.published, post.failed and competitor.breakout, and let your automations react.
The full pipeline, programmable
The API is the same guarded machine the dashboard drives — never a side door around your brand's rules.
Create drafts or schedule directly; review-first is the default, always.
Scored drafts written in your voice from any topic, URL, doc, or PDF.
Upload media (multipart included) and apply any of the 52 studio templates.
me, posts and createPost as one typed graph — same keys, same guardrails.
HMAC-signed, retried deliveries the moment a post publishes, fails, or a tracked account breaks out.
Per-key scopes and per-key rate limits; a read-only key can never publish.
Publishes natively to
Developer questions
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.
Mint one in Settings → API keys inside the dashboard. Keys are scoped (read, publish, generate, media), shown once, and revocable in one click. Send them as `Authorization: Bearer krv_...` or `X-API-Key`.
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.
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.
API & MCP access is included from the Plus plan up — no separate developer tier, no extra metering surprise.
Automate the repetitive parts. Keep the creative ones.
API & MCP access is included from the Plus plan up.
Invite-only beta. One click with Google or Microsoft — no forms, no spam.