For developers
Build your workflow on the Krevaya API
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.
API access is included from Plus up.
curl --fail-with-body https://api.krevaya.com/v1/posts \
-H "Authorization: Bearer $KREVAYA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"platform": "linkedin",
"body": "Our repair intake checklist starts with a description of the problem."
}'
# HTTP 201; status is "draft", and id is a string.
# Omitting brand_id uses the currently selected brand.POST https://api.krevaya.com/graphql
mutation {
createPost(input: {
platform: "linkedin"
body: "Our repair intake checklist starts with a description of the problem."
}) {
id
status # "draft" — waits in your review queue
}
}import os
import requests
r = requests.post(
"https://api.krevaya.com/v1/generate",
headers={"Authorization": "Bearer " + os.environ["KREVAYA_API_KEY"]},
json={
"text": "Our repair intake checklist records the symptom, when it started, and how to reproduce it.",
"instruction": "Create practical drafts without adding claims.",
},
timeout=600,
)
r.raise_for_status()
result = r.json() # synchronous: source_id and post_ids
print(result["post_ids"])const r = await fetch("https://api.krevaya.com/v1/posts", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.KREVAYA_API_KEY}`,
"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();
if (!r.ok) throw new Error(JSON.stringify(post));
// post.id is a string; post.status is "draft".What the API covers
Posts and scheduling
Create a draft for review or set a future publishing time. Your existing publishing rules still apply.
Writing and design
Generate drafts in your voice, upload assets, and apply your studio templates.
REST, GraphQL and MCP
Use the REST API, the GraphQL beta, or the hosted MCP server with the same scoped keys.
Events and webhooks
Receive HMAC-signed events when posts publish or fail, with up to three attempts for transient delivery failures.
Start with a scoped key
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.
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.
Connect your workflow
Create drafts or schedule posts with your key. Register signed webhooks using a dashboard session to receive publication outcomes.
Authentication and limits
One key works across REST, GraphQL and MCP, limited to the scopes you gave it.
- Base URL
https://api.krevaya.com- Authentication
- Authorization: Bearer krv_... or X-API-Key
- Scopes
- read, publish, generate, media, engage
- New posts
- A draft for review, unless you send a future schedule_at. Pinterest and Tumblr posts always land as drafts.
- GraphQL
- Beta: me, posts and createPost, with the same keys as REST
- Webhooks
- HMAC-signed, up to three attempts for transient delivery failures
- Plan
- Plus and up. Account request limits, generation allowances, and operation-specific credit costs still apply.
Questions from developers
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`.
Does creating an API post schedule it?
Omit schedule_at to create a draft for review. Supply a future schedule_at to authorize scheduling directly. The MCP schedule_post tool also approves a draft when scheduling it. Pinterest and Tumblr posts always land as drafts instead, and you approve each one in Krevaya. Safety screening, account permissions, and plan limits still apply.
Is GraphQL production-ready?
GraphQL is in beta and exposes me, posts, and createPost with the same keys as REST. Use REST for source generation, assets, and brand memory, and MCP for operations such as scheduling existing posts, editing individual layers, and polling jobs.
Which plans include API access?
API and MCP access starts with Plus. Account request limits, generation allowances, and operation-specific credit costs still apply.
Start building on Krevaya
API and MCP access are included from the Plus plan up.
Try a plan for 7 days. Card required.