A REST API for the two things people actually want to automate: getting content into the queue from somewhere else, and getting performance data into a warehouse or a client dashboard you already run. Included on the Agency plan.
Used by leaders from
Deliberately small. A wide API nobody uses is worse than a narrow one that covers the real cases.
List the accounts you publish to, with their status and voice profile. The id from here is what everything else is keyed on.
Create a draft against an account, optionally in review. This is the endpoint most people actually want: content from your CMS, your CRM or a script, straight into the queue.
Give a draft a time, or let it take the next open slot. Same rules as the calendar, including approvals.
Per post and per account, over any range you kept. Enough to feed a warehouse or a client dashboard without screenshotting anything.
Worth being explicit, because “we’ll do it via the API” is often how people expect to bypass a constraint.
A draft created through the API on an account that requires sign-off goes into review, exactly as it would in the app. There is no parameter that skips it.
Publishing goes through the official integration whichever door you came in by. The API cannot post faster than LinkedIn allows, and it will tell you honestly when it is being throttled rather than silently dropping things.
A token reaches exactly the accounts your workspace has, and no more. Rotate or revoke it from settings; nothing else needs touching when someone leaves.
Still honest about maturity: this is a small API built around the cases agencies actually asked for, not a complete surface over every feature. If you need an endpoint that is not here, tell us what you are wiring it into — that is genuinely how the current four got chosen.
The Model Context Protocol server covers most of what people would otherwise script, in a sentence rather than a request body. Included on every plan.
New draft, post published, approval requested. Enough to hook Hypelio into a Notion board or a Slack channel without anyone opening a terminal.
Fire on publish, on approval, and on failure. The failure one matters most: it is how you find out a token was revoked before the client does.
The four endpoints exist because agencies asked for them by name. If yours is missing, that is the fastest way to change it.
API on the Agency plan. MCP on every plan, including Solo.