API · IN DEVELOPMENT

Build autonomous GTM into your product.

The Mergeflo API will expose visibility analysis, content operations, channel publishing, pipeline actions, measurement, and workflow controls through one interface. It is in development and not yet available. This page describes what is planned and how to shape it.

Tell us what you would buildSee the platform

No public endpoints are live today

WHERE IT STARTS

What already runs underneath.

The API is not a new system. It is an interface onto the one the product already runs on, which is why it is worth being precise about what exists today.

One ingress, one identity check
Every internal call already passes through a single gateway that verifies the caller and attaches a verified workspace identity. An API key becomes another way to authenticate at that same door.
Workspace isolation
Data is scoped per workspace throughout, so multi-customer separation is a property of the system rather than something the API layer has to invent.
An action record
Decisions, approvals, changes and results are already written to an audit trail. Exposing that history is a read, not a rebuild.
Typed contracts
The data shapes the product uses are defined in one place, which is what makes stable, versioned responses realistic rather than aspirational.

PLANNED

What the first release aims to cover.

Read access first. Endpoints that spend money or contact a person will follow once keys, limits and stop controls have been proven in the open.

Start with one key (planned)
Scoped keys, a test mode, versioned endpoints, and error responses that say what went wrong.
Read your visibility and measurement (planned)
Search and AI visibility, content performance, and the pipeline and revenue reporting the product already produces.
Usage you can see (planned)
Usage tracked by endpoint, workspace and billing period, so a partner can reconcile what they consumed.
Reliable workflows (planned)
Webhooks, idempotency keys, retries and rate limits, so an integration can be built to survive a bad afternoon.
Serve multiple customers (planned)
Isolated workspaces with their own limits and reporting, for agencies and partners running Mergeflo on behalf of others.

HELP US SCOPE IT

The order depends on what you need.

If you are considering building on Mergeflo, tell us which endpoint would unblock you and roughly what volume you expect. That is what decides the order, and early answers carry the most weight.

Tell us what you would build

QUESTIONS

Common questions.

Can I get access today?
No. There are no public endpoints and no keys to issue yet. Contact us and we will tell you when that changes rather than putting you on a list that goes quiet.
Will it be read-only?
At first, yes. Write endpoints spend money and contact real people, so they follow once scoped keys, rate limits and stop controls are proven.
Is there a timeline?
Not a published one. We would rather name a date once the first endpoints are running than commit to one now.
What can I use in the meantime?
The product itself, and the connections on the integrations page. Those are live today and marked live or planned so you can see exactly which is which.

EXPLORE

Available now.

Integrations
Every connection, marked live or planned.
Automation
Approvals, limits, policies and stop controls per workflow.
Measurement
Content, channels, outreach, opportunities and revenue in one view.
The platform
What Mergeflo runs today, end to end.

GET STARTED

Put your GTM work in one system.

Create content, reach buyers, and measure revenue with the control level your team needs.

Start freeBook a demo