Mixpost App Mixpost API
✓ Official Vendor SpecSocial MediaSocial Publishingbearer22 EndpointsREST
For 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.
Use for: I want to schedule a post for tomorrow at 9am across LinkedIn and X, Upload an image to Mixpost media, List all connected social accounts, Create a new tag for campaign tracking
Not supported: Does not handle social listening, ad management, or DM inbox — use for Mixpost post scheduling, media upload, and account management only.
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.
Install Jentic One Beta
Connect the Mixpost API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mixpost API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Mixpost API.
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
Patterns agents use Mixpost API for, with concrete tasks.
★ 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.
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.
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.
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.
Use Jentic to find the Mixpost create post operation and execute it with generated copy and a previously uploaded media ID
Key Endpoints
22 endpoints — the mixpost api drives mixpost, a self-hosted social media management platform for scheduling and publishing posts across multiple networks.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Mixpost bearer tokens are stored encrypted in the Jentic vault. Agents call media upload and post creation through Jentic and never see the raw Authorization token.
Intent-based discovery
Agents search Jentic with intents like schedule social post or upload media to mixpost and Jentic returns the matching Mixpost operation with input schema and example.
Time to first call
Direct Mixpost integration: 1-2 days to wire auth, chunked upload, and post scheduling. Through Jentic: under 1 hour to search, load, and execute a scheduled post.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Mixpost API through Jentic.
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.
GET STARTED