Overview
Use eksis as the social media backend of your own product, with your customers' channels in one workspace.
This section is for developers who build a product on top of eksis. Your customers connect their Instagram, Facebook, or other accounts from inside your app, and your server reads and answers through the eksis API. eksis holds the platform connections, refreshes their tokens, receives the platform's own webhooks, and applies each network's rules. Your app keeps the business logic and knows which channel belongs to which customer.
The running example in these pages is a service for online shops: when a shopper sends an Instagram DM, the service searches the shop's catalog and answers with product cards. The same pieces fit a scheduling tool, a comment moderation service, or an agency dashboard.
How the pieces fit
Your customer ──signs in──▶ Instagram / Facebook / ...
│ │
│ uses your app │ messages, comments, publishing
▼ ▼
Your server ◀──webhooks──── eksis workspace (many channels)
│ ▲
└──── REST API calls ──────┘Your customer connects a channel
Your app calls POST /v1/connect and sends the customer to the sign-in page it returns. The consent screen shows eksis. After sign-in the customer comes back to your app, and you connect the account they picked. See Connect your customers' channels.
eksis tells your server what happens
A webhook endpoint receives message.received, comment.received, publishing results, and channel problems. Each event names the channel it belongs to. See Receive events.
Your server answers
Reply to a direct message with text, an image, or product cards, answer a comment, or schedule a post for that customer's channel. See Direct messages, Comments, and Publishing.
What you need
- A workspace on Pro Eksis or Super Eksis. The REST API, webhooks, and direct messages start on Pro Eksis. Prices are on the pricing page.
- An API key from the API & MCP page of that workspace. Steps: Introduction.
- A public HTTPS address on your server for webhooks.
- A table in your own database that maps each customer to their eksis channel ids.
What the API does not do
- Create workspaces or API keys. Both are made in the eksis app.
- Disconnect a channel. In the app, open Settings, Channels, and choose Disconnect on it.
- Start a direct message conversation. Platforms open a reply window only after the person writes first.
Pages in this section
Workspaces and limits
One workspace for many customers, and the numbers each plan allows
Connect your customers' channels
The sign-in flow, the return to your app, and repairing a broken channel
Receive events
Route each webhook to the right customer and handle retries
Direct messages
Reply with text, an image, a video, or up to 10 product cards
Comments
Read, answer, hide, and turn a comment into a DM
Publishing
Schedule and publish posts on your customers' channels
Limits and errors
Quotas, the 429 answer, and which errors to retry
Go live
Platform terms, customer data, and a checklist before launch
Example: a DM bot
A complete Node.js handler that answers DMs with product cards