Mixpost API
The Mixpost REST API lets third-party services create, schedule and manage social media content on your own Mixpost instance.
Base URL
Every endpoint is served from your own installation, under /api:
https://example.com/api
From Pro v7 and Enterprise v8 the MIXPOST_CORE_PATH environment variable is
empty by default, so Mixpost runs at the root of your domain. Earlier versions,
and Mixpost Lite, default it to mixpost; if your instance sets a core path, every
path moves under that prefix — https://example.com/{corePath}/api. Replace
example.com with your instance host.
Editions
Endpoints tagged Workspaces, Subscriptions, Users and Receipts are served from the admin panel of Mixpost Enterprise only. All other endpoints are available in Mixpost Pro and Enterprise.
Authentication
- HTTP: Bearer Auth
Mixpost access token, sent as Authorization: Bearer <token>.
The token is read from the Authorization header only — there is no query-string, cookie, or custom-header fallback.
Creating a token. Tokens are created from the Access Tokens page in the dashboard. You give the token a name and an expiry: 7, 30, 60 or 90 days, a custom date, or never expires. The token value is shown exactly once at creation and is stored hashed, so it can never be retrieved again — copy it immediately. A token is rejected once its expiry date has passed.
Tokens have no scopes. A token carries no abilities of its own: it inherits the full authority of the user who created it. Which endpoints it can reach is determined entirely by that user's workspace role (see the role matrix below), not by anything set on the token.
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
License
Proprietary