Developers
Automate social media posting.
Connect n8n, Make, your own app or an AI agent, and your social media posts get written in your voice and scheduled without opening Buzzmark.
A new blog post becomes a LinkedIn draft, a launch fills next week, and every post lands on your calendar first.
Included on every plan.
7 days free for new users.
Pick how you connect.
REST API
From your workflows and apps
Send posts from n8n, Make or your own code, and hear back the moment one goes out.
GET /api/v1/meCLI
From a terminal or a script
Let Claude Code, Codex or a nightly script write and schedule posts with one command.
npx buzzmark list-social-setsMCP server
From an AI agent
Connect Cursor, Claude Code or any MCP client, and ask for posts in your own words.
https://buzzmark.ai/mcpWhat you can automate.
The repetitive part goes to a workflow. You keep the final say.
When your feed updates, n8n or Make asks Buzz for posts about it in your voice.
Posts about a new article
curl -X POST "https://buzzmark.ai/api/v1/write" \
-H "Authorization: Bearer $BUZZMARK_API_KEY" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{
"idea": "Our spring menu launches Friday: seven new dishes from farms within 50 km",
"platform": "instagram",
"count": 3
}'Up to 25 posts in one request, from a sheet or your CMS. If one wouldn't go out, nothing is saved.
Schedule several posts
curl -X POST "https://buzzmark.ai/api/v1/posts/bulk" \
-H "Authorization: Bearer $BUZZMARK_API_KEY" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{
"posts": [
{
"post_id": 401,
"when": "next_slot"
},
{
"social_set_id": 12,
"text": "Sunday brunch is back.",
"when": "2026-12-06T09:30"
}
]
}'Claude Code, Codex or OpenClaw asks for next week and gets a post for every slot, timed to your best hours.
Terminal
npx buzzmark create-weekly-content-plan --social-set-id 12 --goal "Fill the week before our spring launch"
Your server gets a signed message when a post goes out, fails or an account needs reconnecting, so the next step runs on its own.
post.published
{
"id": "evt_7d1f0c2a9b4e4f6c8a3b5d9e1f2a4c6b",
"type": "post.published",
"created": 1763215200,
"data": {
"post_id": 408,
"social_set_id": 12,
"status": "published",
"scheduled_at": "2026-11-15T14:00:00Z",
"accounts": [
{
"account_id": 51,
"platform": "linkedin"
}
]
}
}One key. You stay in control.
It works in the API, the CLI and any AI app that can't sign in.
- Where
- AI apps, under Keys. It's shown once, and Buzzmark keeps only its fingerprint.
- What it can do
- Read, Draft or Schedule. A read key stays read-only in the API, the CLI and AI apps.
- Who it acts as
- The person who made it, with their role and their brands. A contributor's key can't schedule through the API.
- How many
- Growth 3, Reach 5, Scale 10 and Agency 25 live keys for the whole organization.
- How long
- Never expires unless you pick 30 days, 90 days or a year. Revoke it any time and it stops within a minute.
Rather ask in a chat?
Ask Claude, ChatGPT or Grok for a post or a whole week in your own words. No code.
Questions about building on Buzzmark
The API for n8n, Make or your own code. The CLI for agents and scripts in a terminal. The MCP server for AI apps that connect directly.
Yes, with your plan's own monthly amounts for writing and pictures.
No. The most they can do is schedule a post at least 5 minutes out, where you can still move it or take it back.
No. Reading and scheduling cost nothing. What Buzz writes, Hive checks and pictures use your plan's monthly amounts.