canonical: https://jentic.com/apis/mixpost.app/mixpost # Mixpost App Mixpost API The Mixpost API drives Mixpost, a self-hosted social media management platform for scheduling and publishing posts across multiple networks. The 22 endpoints cover connected social accounts, post drafting and scheduling, media upload (including chunked and remote uploads), and tag management. Posts can be queued, scheduled to a specific time, or routed through an approval workflow before publishing. ## For AI agents Schedule, publish, and manage social media posts and media across connected accounts in a self-hosted Mixpost instance, with support for queues, scheduling, and approvals. ## Scope Does not handle social listening, ad management, or DM inbox - use for Mixpost post scheduling, media upload, and account management only. ## Capabilities - List, create, and update connected social media accounts - Draft, schedule, and publish posts across multiple networks - Upload media via standard, chunked, or remote URL upload - Tag posts and accounts for organisation and reporting - Move posts through queue and approval workflows - Retrieve scheduled and published post history ## Use cases ### Multi-Channel Scheduling A marketing team uses Mixpost as their self-hosted social hub and posts content to multiple networks simultaneously. The API accepts a single post payload that targets several connected accounts, with optional scheduling time and per-network text variants. Teams that need data residency control choose Mixpost over hosted SaaS schedulers and drive it via API from their CMS or workflow tool. Example prompt: Create a scheduled post via POST /posts targeting accounts {acc1, acc2} with text and media at 2026-06-12T09:00:00Z ### Media-Heavy Campaign Workflows Campaigns with large videos or many images use the chunked and remote upload endpoints to ingest media into Mixpost without timing out the request. After upload the media IDs are referenced by post creation calls. This separates the heavy upload step from the lightweight scheduling call so retries and progress reporting are simpler. Example prompt: Upload a 200MB video via POST /media/chunked-upload, then attach the returned media ID to a new scheduled post ### Approval Workflow Integration Larger teams require posts to be reviewed before publishing. Mixpost's approval flow can be driven through the API so an external review tool reads pending posts, surfaces them in its own UI, and returns approve or reject decisions. The approver's identity and timestamp are captured in Mixpost for audit. Example prompt: List posts in pending approval state via GET /posts and post the approval decision back for each reviewed item ### Agent-Driven Content Pipeline An agent discovered through Jentic generates copy, attaches assets, and schedules the resulting post in Mixpost without operator intervention. Jentic stores the bearer token in its credential vault, so the agent invokes media upload and post creation operations without ever holding the raw API key for the Mixpost instance. Example prompt: Use Jentic to find the Mixpost create post operation and execute it with generated copy and a previously uploaded media ID ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /accounts | List connected social accounts | | POST | /media | Upload media for use in posts | | POST | /media/chunked-upload | Upload large media in chunks | | POST | /media/remote-upload | Upload media from a remote URL | | GET | /tags | List tags | ## Key resources - **Accounts** — Connected social media accounts - **Media** — Uploaded images and videos for posts - **Posts** — Drafted, scheduled, and published posts - **Tags** — Labels for organising posts and accounts ## Why Jentic - **Setup:** Wiring the Mixpost API by hand means handling its bearer auth, resolving your self-hosted host and core path template, and coding the chunked and remote media upload steps yourself. Through Jentic you install once, import the Mixpost API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Mixpost's post and media targets travel in the request body rather than the URL path, so scope your agent by limiting it to the operations it needs, such as listing accounts and uploading media. You leave out account management so the agent schedules content without changing connected social accounts. - **Credential handling:** Your Mixpost token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'upload media to Mixpost' or 'list connected accounts', and Jentic returns the matching Mixpost operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Buffer API** — Hosted social media scheduling platform - **Sprout Social API** — Enterprise social management and analytics - **OpenAI API** — Generate post copy and image prompts ## FAQ ### What authentication does the Mixpost API use? The Mixpost API uses bearer token authentication. Generate a token in the Mixpost admin and pass it in the Authorization header on every request. Through Jentic the token is held in the credential vault and injected at execution time. ### Can I schedule a post across multiple accounts at once? Yes. POST /posts accepts an array of target account IDs along with the post body and an optional scheduled time. Mixpost handles fan-out to each connected network and reports per-account publishing status. ### What are the rate limits for the Mixpost API? Because Mixpost is self-hosted the rate limits are determined by the operator's instance configuration rather than a vendor. The downstream social networks Mixpost publishes to (LinkedIn, X, Facebook, etc.) impose their own limits which Mixpost respects when fanning out. ### How do I upload a large video to Mixpost through Jentic? Search Jentic for chunked upload mixpost, load the schema for POST /media/chunked-upload, and execute with the file part. Once the upload completes use the returned media ID when creating the post. ### Does the Mixpost API support post approval workflows? Yes. Posts can be created in a pending approval state and moved through approve or reject transitions via the posts endpoints. The reviewer identity and timestamp are recorded for audit. ### Can I tag posts for campaign tracking? Yes. Use the /tags endpoints to create tags, then attach tags when creating or updating a post. Filtered listing of posts by tag supports per-campaign reporting. ### Can I limit what my agent is allowed to do with the Mixpost API? Yes. Because you run Jentic One yourself, your own rules decide which Mixpost operations and credentials the agent can use, so you can grant it just the calls it needs, such as listing accounts and uploading media through POST /media, POST /media/chunked-upload, or POST /media/remote-upload. Since Mixpost's post and media targets travel in the request body rather than the URL path, you scope the agent at the operation level and leave out account management endpoints. That way the agent can draft and schedule content without altering your connected social accounts.