Overview
The MissLess Social API gives your product Facebook and Instagram features without running your own Meta app. Your users connect their Pages and Instagram accounts with one consent screen. You call one REST API to publish, schedule, read the inbox and reply. A widget and an MCP server sit on top of the same API.
Base URL: https://social.missless.tel/v1
The tech-provider model, in plain words
Section titled “The tech-provider model, in plain words”Meta requires every app that publishes content or reads messages to pass app review and business verification. MissLess has done that once, for one Meta app. You do not register an app, you do not go through review, and you never handle a Meta access token.
What your users see is a consent screen from Meta. They pick the Pages and Instagram accounts to connect, click allow, and come back. From that moment your API key can act on those accounts.
Tokens are stored encrypted on the MissLess side and refreshed by MissLess. When a token expires or a user revokes access, you get a webhook and the account shows expired or revoked.
Two-level tenancy
Section titled “Two-level tenancy”| Level | What it is | Example |
|---|---|---|
| Partner | Your product. Owns API keys, the webhook endpoint, and every workspace beneath it. | A scheduling tool for salons |
| Workspace | One customer of your product. Owns connected accounts, media, posts and conversations. | One salon |
| Account | One connected Facebook Page or Instagram professional account inside a workspace. | The salon’s Instagram |
Create a workspace per customer, with your own user id as external_id. Every other object hangs off a workspace. Keys are either partner-wide or scoped to one workspace. See Concepts.
API first, widget optional
Section titled “API first, widget optional”Everything is reachable over /v1. The hosted connect page and the embeddable widget are conveniences built on the same endpoints.
- API. Workspaces, connect links, accounts, media, posts, conversations, webhooks. Start with the Quickstart.
- Widget. A composer, calendar, inbox and accounts screen you embed in an iframe. Sessions are minted server-side, the look follows your theme. See the Widget overview.
- MCP. An MCP server so an AI assistant can publish and reply on one workspace. See the MCP overview.
What you can do
Section titled “What you can do”| Area | Facebook Page | Instagram professional account |
|---|---|---|
| Publish | Text, link, single photo, multi-photo, video | Image, carousel (2 to 10 items), Reels |
| Schedule | Yes | Yes |
| Inbox | Messenger DMs, comments on Page posts | Instagram DMs, comments on media |
| Reply | DM reply, comment reply, private reply to a comment | DM reply, comment reply, private reply to a comment |
| Stats | Followers, follows, media count | Followers, follows, media count |
Other networks are not part of v1. The contract is written so they can be added behind the same endpoints later.
Where to go next
Section titled “Where to go next”- Quickstart: from an empty partner account to a published post in five calls.
- Authentication: key kinds, headers, rate limits, errors.
- Connect links: the hosted flow your users go through.
- Webhook setup: how results come back to you.