Use the Beeive API to create posts, upload media, manage channels and read
analytics from your own code.
https://app.beeive.com/public/v1
Send your API key in the Authorization header of every request, as is ,
without a Bearer prefix:
curl https://app.beeive.com/public/v1/integrations \
-H " Authorization: YOUR_API_KEY "
Your API key is under Settings → Developers → Access in the Beeive app.
API access is included on every paid plan.
Building for other Beeive users?
The API key only acts on your own account. To act on behalf of other Beeive
users, create an OAuth app . The access tokens it
receives start with pos_ and go in the same Authorization header.
The MCP server uses a different format
The MCP server expects Authorization: Bearer YOUR_API_KEY. The REST API expects the key on its own.
Errors return a JSON body with a msg field:
Status
msg
Meaning
401
No API Key found
The Authorization header is missing.
401
Invalid API key
The key is wrong or has been rotated.
401
Invalid OAuth token
The pos_ token is wrong or was revoked.
401
No subscription found
The account has no active paid plan.
400
Varies
The request is invalid. For posts, the message says which channel rejected it and why.
429
Too many post-creation requests. See Limits .
Creating posts (POST /posts) is limited to a set number of requests
per hour for each account. Over the limit, you get 429 Too Many Requests:
wait before retrying. One request can post to several channels at once, so
batch where you can.
Posts also count toward your plan’s monthly post allowance , just like
posts created in the app.
Other endpoints aren’t rate-limited.
Method
Path
Description
GET
/is-connected
Check that your key works. Returns { "connected": true }.
GET
/notifications
Your account notifications, paginated with ?page=0.