API & Developers
The API is being built. Tell us what to expose first.
Authentication and brand-scoped keys are done. The endpoints on top of them are not — so rather than publish a reference to something that is not there, we are asking what you would actually use.
- Private development
- No date promised
- Waitlist open
Straight answer first: you cannot build anything useful on this today. One read-only endpoint is live and it returns a brand’s team members. Publishing, analytics and auto-reply management are not available programmatically. If you need those now, the API is not ready for you — and we would rather you heard it here than after signing up.
Where it stands
Three things are true at once, and they are worth separating.
Built
Key generation and hashing, prefixes, brand scoping, scope enforcement, revocation and Bearer authentication. The plumbing is real.
Exposed
One read-only endpoint, returning the members of a brand. That is the entire public surface.
Not yet
Publishing, scheduling, analytics, auto-reply rules, connecting accounts. All exist as dashboard routes; none accepts a key.
Progress shows up on the changelog as it lands, with no dates attached ahead of it.
What people keep asking for
These four come up most. If yours is not here, that is the useful thing to tell us.
Publish from your own system
Push from a CMS, a PIM or an internal tool straight into the queue, so the people writing never open Mediux at all.
Pull analytics somewhere else
Get reach, engagement and ROAS into a warehouse or a client-facing dashboard on your own schedule.
Automate brand onboarding
Agencies signing a new client: create the workspace, invite the team and seed the calendar in one scripted step.
Wire engagement into your stack
Route unanswered comments and DMs into the helpdesk you already run, instead of a second inbox nobody watches.
Join the waitlist
Small enough list that what you describe genuinely affects the order things get exposed in.
How it will work
The authentication model is settled, so you can judge whether it fits before you join.
A brand-scoped key, sent as a Bearer token. Keys are prefixed mk_live_, belong to exactly one brand, and are returned once at creation — we keep a hash and a short prefix, never the secret.
The shape, today
curl https://mediuxai.com/api/brands/$BRAND_ID/members \
-H "Authorization: Bearer $MEDIUX_API_KEY"Brand-scoped
A key for one client workspace cannot reach another — the same wall the dashboard enforces.
Scoped further
Keys carry a scope list. A key created with an empty list is treated as having all of them, so scope production keys explicitly.
Revocable
Revoke and it stops immediately. Rotation is creating a new key and deleting the old one.
Already a customer and want the one live endpoint switched on for your brand? Email us — issuance is manual while the surface is this small.
Questions
- Why a waitlist rather than documentation?
- Because there is not enough to document. Authentication, brand-scoped keys, hashing, scope checks and revocation are all built and working — but the endpoints on top of them are not, and publishing a reference for routes that do not exist would waste your afternoon.
- What exists today?
- One read-only endpoint accepts a key: it returns the team members on a brand. That is the whole public surface. Nobody integrates a platform to read their own team list, so we are not pretending it is a developer product yet.
- What does joining actually get me?
- Early access when the first useful endpoints land, and real influence over which ones those are. The list is small enough that what people describe genuinely decides the order.
- When will it be ready?
- No date, deliberately. A roadmap with dates on it is a promise, and we would rather ship the thing than manage the promise. Progress appears on the changelog as it happens.
- Will it cost extra?
- Not decided. The likeliest answer is that it follows your plan rather than becoming a separate line item, but we are not going to commit to pricing for something unbuilt.
- I need this now. What are my options?
- Tell us — if your use case is close to something already half-built, that moves it up considerably. If you need programmatic publishing today, we would rather say so than have you sign up and find out.
Still stuck, or want a hand setting something up?