MCP and API

Create, schedule, and query Flux posts through API or AI

Connect Flux to an external system through the API or to an AI assistant through MCP. Beyond querying projects, posts, and approvals, you can now create, edit, and approve content through these integrations.

Start your free 7-day trial Learn about Flux

New: with Webhooks, Flux notifies your systems when a post is published, when publishing fails, and when someone makes an approval decision.

Two ways to reach the same data

The API lets an external system query and feed Flux programmatically. An agency could, for example, create posts from its own management system, pull approvals into an internal dashboard, or check every day what's still waiting for review.

MCP connects Flux to AI assistants, like Claude Code. You can ask for the same information and have the assistant create, edit, or approve posts in natural language, without opening the Flux dashboard or building an integration of your own.

What you can ask through MCP

Which posts are waiting for approval this week?

5 posts waiting for approval.
2 from Padaria Aurora, 2 from Cotta Studio, and 1 from Loja XPTO. The Padaria Aurora post has been stuck for 3 days, waiting on Ana Lima's review.

Create a Padaria Aurora post with this photo and the caption for Friday's menu, and send it for approval.

Post created and sent for approval.
It shows up in the Padaria Aurora project as waiting for approval. Once the client approves it, you just need to schedule it.

"What's scheduled for the Padaria Aurora client?""Schedule this Cotta Studio Reel for Thursday at 6 p.m.""Change the caption on tomorrow's Loja XPTO post.""Is any project missing a connected social account?""Which posts got requested changes?"

What you can do through the API and MCP

Both integrations give access to the same actions. On top of querying, you can now handle content end to end without going into Flux.

Upload media

Upload photos and videos to use in new posts.

Create posts

Create content and choose whether it stays as a draft, goes out for approval, or gets scheduled right away.

Edit posts

Change the caption, media, or date while the post hasn't been published yet.

Log approvals

Approve a post or request changes directly through the integration.

When you create content for TikTok or Pinterest through MCP, the assistant asks for the required settings before sending it: the privacy options on TikTok and the board on Pinterest. The post is only sent after you confirm.

What you can query

Projects: projects available on the account and their connected networks.
Posts: posts, captions, media, status, and scheduling or publish dates.
Approvals: number of approvals, requested changes, and pending reviewers.
Approval history: who approved, who requested changes, and the comments logged.
Approval groups: posts grouped for review and the progress of each one.
Social accounts: connected, disconnected, or expired accounts.
Multi-network content: different versions of the same content published across more than one network.

Webhooks: Flux notifies your systems

With Webhooks, Flux sends an automatic notification to an external system when something happens, so that system doesn't need to keep polling the API. You set the URL that receives the notification and choose the events that trigger it.

Event	When Flux sends it
Post created	A new post is created in Flux.
Post updated	An existing post is changed.
Post scheduled	A post is scheduled for publishing.
Post deleted	A post is removed.
Post published	The post is published successfully.
Publishing failed	Flux tries to publish, but publishing doesn't go through.
Approval decided	Someone approves the content or requests changes.
Account disconnected	A connected social account loses its connection.
Account reconnected	That account's connection is restored.

Here's an example: an agency with its own task system subscribes to the “Post published” and “Publishing failed” events. When the post goes live, the task is marked as done. If publishing fails, the system creates an alert for the team.

Each notification comes with a signature that lets your system confirm it was sent by Flux. If the URL doesn't respond, Flux keeps retrying for a few days. If the failures continue, the Webhook is turned off.

How to turn it on

Go to settings
Inside Flux, go to Company settings, then API.
Pick your option
Integration guide to connect an AI assistant through MCP, Create token to use the API, or the Webhooks tab to set up notifications.
Follow the steps
Connect your assistant or system and start using it.

Before you use it

Posts scheduled through the API or MCP are published automatically at the set date and time, with no extra confirmation, just like scheduling in the app. Drafts and posts sent for approval aren't published on their own and need to be scheduled later.
Editing is only possible while the post hasn't been published yet.
Each key is limited to 120 requests per minute and 20 create or edit actions per minute.
Each account can set up to 5 Webhooks.
Media links returned expire after 48 hours.

Documentation for developers

The full setup guide, with request examples, is available for whoever implements the integration.

API documentation ↗MCP integration guide ↗

More organization to create, approve, and publish.

Frequently asked questions

Can I create or edit posts through the API or MCP?

Yes. You can upload media, create posts as drafts, send them for approval or schedule them, edit the caption, media, or date while the post hasn't been published, and log approvals or requested changes.

Is a post scheduled through the API or MCP published automatically?

Yes. It's published at the set date and time, with no extra confirmation, just like in the app. Drafts and posts sent for approval need to be scheduled later.

What are Flux Webhooks?

They're automatic notifications Flux sends to an external system when a chosen event happens, like a published post, a publishing failure, or an approval decision. You'll find them in Company settings, under API, in the Webhooks tab.

What's the usage limit?

Each key is limited to 120 requests per minute and 20 create or edit actions per minute. Each account can set up to 5 Webhooks.

Do the media links returned last forever?

No. They expire 48 hours after being generated.

Which AI assistants work with Flux's MCP?

Any assistant compatible with the Model Context Protocol, like Claude Code. The integration guide inside Flux walks you through the connection.

Do I need to build something to use the API?

Yes, the API and Webhooks are for anyone with their own system, dashboard, or automation that will connect to Flux. If you just want to query or create posts in natural language, MCP is the simpler path.