Use Buzzmark from your own code
Buzzmark's REST API lets your code, n8n or Make read your social sets, save drafts, check posts against each platform's rules and schedule them, with a personal key.
It can also add pictures and videos, have Buzz write and check posts in your brand's voice on your plan's monthly quotas, and read how your posts did.
A key acts as you, with your role and brands. Nothing posts right away, and every request that creates something takes an Idempotency-Key, so a retry never posts twice.
A time without an offset is on the social set's clock. Signed webhooks tell your server when a post goes out, fails or is approved.
What it can do
- Read your social sets, connected accounts, brand profiles, posts and best times.
- Save, change and delete drafts, and check a post before it's scheduled. See Check and schedule posts.
- Schedule a post at a time, at a best time or in the next free slot, one at a time or in bulk, and move, take back or retry it.
- Add pictures and videos by upload or by link, or have Buzz make a picture. See Pictures and video.
- Have Buzz write, rewrite, check and adapt posts in your brand's voice. See Buzz writing.
- Read how each post did on each platform. See Post stats.
- Get a signed request on your server when a post goes out, fails or is approved. See Webhooks.
Every plan has the API, and every request follows the app's own rules: each platform's limits, Buzz's writing rules and your plan's monthly amounts.
Make a key
1. In Buzzmark, open Settings and go to Developers.
2. Under Personal keys, name the key after where it goes, pick what it can do and when it expires, and press Make a key.
3. Press Copy and keep the key where your code or workflow keeps its secrets. Buzzmark shows it once.
A key reads, drafts or schedules, with your role and brands; Keys and scopes has the detail. The same key works in the CLI and in AI apps without sign-in. Sign-in, keys and limits covers expiring and revoking it.
Send your first request
Every request goes to https://buzzmark.ai/api/v1 with the key in the Authorization header, never in the address. Send JSON with Content-Type: application/json. Start with GET /me: it answers who the key acts as and what it can do.
Terminal
curl https://buzzmark.ai/api/v1/me \ -H "Authorization: Bearer $BUZZMARK_API_KEY"
An answer that worked is {"ok": true, "data": …}. A refusal is {"ok": false, "error": {…}} with a code to build on, a message to show a person, retryable, and the request_id that the X-Request-Id header also carries. The HTTP status matches the code. Errors and limits lists every code.
Read your account
| Endpoint | Request | Needs |
|---|---|---|
| Who the key acts as | GET /api/v1/me | Read |
| List social sets | GET /api/v1/social-sets | Read |
| List connected accounts | GET /api/v1/channels | Read |
| List brand profiles | GET /api/v1/brand-profiles | Read |
| Best times to post | GET /api/v1/best-times | Read |
Most other requests take a social_set_id and account ids from GET /social-sets. A post written for another brand than its set's own takes a hive_profile_id from GET /brand-profiles.
Times
- A time with an offset, such as
2026-12-04T18:00:00+01:00, is that moment. - A time without one, such as
2026-12-04T18:00, is on the social set's clock. best_timepicks the soonest free hour when the accounts' posts do best, andnext_slottakes the set's next free posting slot.
A set with natural times on moves a named time a few minutes either way; the answer says the real time.
What stays with you
The API can't post right away: the most it can do is put a post on your calendar, where you can still change it or take it back. It can't delete a scheduled or published post, change your plan, billing or sign-in, or reach accounts that aren't connected to your Buzzmark.
Where to next
- Keys and scopes
A Buzzmark API key, made in Settings under Developers, has one scope: Read, Draft (reads too) or Schedule (reads and drafts too).
- Check and schedule posts
POST /posts/validate checks a post against each account's platform rules and saves nothing; POST /posts and POST /posts/bulk run the same check, then schedule.
- n8n and Make
n8n and Make call the Buzzmark API from n8n's HTTP Request node or Make's HTTP module, with your key in the Authorization header.
- Endpoints
Every endpoint of the Buzzmark REST API, with its method and path, the key scope it needs, its inputs and a curl example to copy into code, n8n or Make.