Buzzmark API
Turn any trigger into a scheduled post.
The Buzzmark API turns a blog post, a launch or a form into a social media post in your brand's voice, scheduled at your best times from n8n, Make or your own code.
Every post is checked against each platform's rules before it reaches your calendar, and a workflow that runs twice still posts once.
Included on every plan, with webhooks.
7 days free for new users.
Check a post before it's scheduled
curl -X POST "https://buzzmark.ai/api/v1/posts/validate" \
-H "Authorization: Bearer $BUZZMARK_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"social_set_id": 12,
"account_ids": [
31,
32
],
"text": "Doors open at 7 tonight.",
"when": "2026-12-04T18:00"
}'Safe to automate.
Workflows retry, time out and run twice. Your feed never shows it.
A retry never posts twice
The same request within 24 hours gets the first answer back.
Checked before it's scheduled
A post that would fail never reaches your calendar. Check without saving while you build.
Nothing posts on the spot
Every post lands on your calendar at least 5 minutes out, where your team can still move it or take it back.
Keys you control
Give a script read-only access, let a teammate's key draft without scheduling, and revoke any key within a minute.
Alerts you can trust
Every webhook is signed, and a failed delivery is sent again.
Your brand's own clock
9:00 means 9:00 where the brand posts, never UTC by accident.
Buzz writing
Drafts in your voice, from any trigger.
A blog post, a product drop or a form becomes a draft in your brand's voice, scored 0 to 100 against how you sound before anyone sees it.
See the writing endpointsOpen studio tomorrow, Saturday, from 11 to 3. Bring a photo of the room that bothers you most and we'll sketch one fix while you have a coffee.
- Match my Hive
- Sharpen it
- Trim it down
- Warmer tone
- Open a thread
Webhooks
Know the moment a post goes out.
Your system hears when a post goes out, fails or an account needs reconnecting, and the next step runs on its own.
See every eventpost.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"
}
]
}
}Read, write and schedule over HTTP.
29 endpoints and an OpenAPI 3.1 file, built from the same definitions the API runs on.
Your account
GET/api/v1/meWho the key acts as
GET/api/v1/social-setsList social sets
GET/api/v1/channelsList connected accounts
GET/api/v1/brand-profilesList brand profiles
GET/api/v1/best-timesBest times to post
Drafts
POST/api/v1/draftsCreate a draft
PATCH/api/v1/drafts/{id}Update a draft
POST/api/v1/drafts/{id}/carouselMake a draft a carousel
DELETE/api/v1/drafts/{id}Delete a draft
Posts
POST/api/v1/posts/validateCheck a post without saving it
POST/api/v1/postsSchedule a post
POST/api/v1/posts/bulkSchedule several posts
GET/api/v1/postsList posts
GET/api/v1/posts/{id}Get a post
POST/api/v1/posts/{id}/rescheduleMove a scheduled post
POST/api/v1/posts/{id}/unscheduleTake a post off the schedule
POST/api/v1/posts/{id}/retrySend a failed post again
Pictures and video
POST/api/v1/media/upload-urlGet an upload link for a file
POST/api/v1/media/from-uploadKeep an uploaded file
POST/api/v1/media/from-urlAdd a picture or video from a link
POST/api/v1/imagesMake a picture
Numbers
GET/api/v1/posts/{id}/statsHow a post did
GET/api/v1/analytics/postsRank recent posts by engagement
Buzz writing
POST/api/v1/writeWrite posts in the brand's voice
POST/api/v1/rewriteRewrite a post
POST/api/v1/checkCheck a post against the brand voice
POST/api/v1/adaptGive a draft a version per platform
GET/api/v1/ideasPost ideas from the news and competitors
GET/api/v1/insightsWhat worked this month
No code? n8n and Make work too.
n8n
Import an endpoint's curl example into an HTTP Request node, and keep the key in a credential.
Make
Send a request from the HTTP module with your key in a header, and parse the answer for the next step.
OpenAPI
Import it into Postman or Insomnia, or generate a client.
OpenAPI file
https://buzzmark.ai/api/v1/openapi.json
What's included.
- Plans
- Every plan, with webhooks.
- Live keys
- Growth 3, Reach 5, Scale 10 and Agency 25, for the whole organization.
- Bulk
- Schedule up to 25 posts in one request, each checked on its own.
- Webhooks
- Up to 10 endpoints, with 8 events and a delivery log that keeps 30 days.
Questions about the API
Yes, with webhooks. Each plan holds a number of live keys for the organization: Growth 3, Reach 5, Scale 10 and Agency 25.
No. The most it can do is schedule a post at least 5 minutes out, where your team can still move it or take it back.
No. n8n's HTTP Request node and Make's HTTP module call it with your key, and the docs have the steps for both.
Same key, same rules. The API is plain HTTP with webhooks, for workflows and your own code. The CLI and the MCP server give AI agents Buzzmark's own tools.
No. LinkedIn and Pinterest don't let their numbers leave Buzzmark, so those posts link to them in Buzzmark.
Reading, drafts and scheduling are included. What Buzz writes, Hive checks, Scout runs and pictures use your plan's monthly amounts.