Workspaces and limits
Keep many customers' channels in one workspace, map them in your database, and know the numbers each plan allows.
An API key reaches exactly one workspace, and the workspace is never part of a request. Everything your app does through that key, from connecting channels to replying to DMs, happens in that workspace and counts against its limits.
One workspace, many customers
The simplest shape for a product built on eksis is one workspace that holds the channels of all your customers. Each customer connects their accounts through your app, and each account becomes a channel with its own id in that workspace.
eksis does not know who your customers are. Keep that mapping in your own database:
create table customer_channel (
customer_id text not null, -- your customer
channel_id text not null, -- data.channels[].id from POST /v1/connect/{sessionId}/select
platform text not null, -- instagram, facebook, ...
primary key (channel_id)
);Every webhook event carries the channel it belongs to, so one lookup in this table tells you which customer an incoming DM or comment is for.
List endpoints such as GET /v1/conversations, GET /v1/comments, and GET /v1/posts return the whole workspace, every customer at once, unless you filter them. Whenever you read for one customer, pass that customer's channel ids in channels. Before acting on a conversation, comment, or post by its id, check that its channel belongs to the customer.
When to use more than one workspace
Use a separate workspace only when you need something a workspace holds on its own:
- Billing. Each workspace has its own plan. A customer who pays eksis directly needs their own workspace.
- A team. Members and their roles belong to a workspace. A customer whose staff also log in to the eksis app needs their own.
- Limits. Channels, the daily request quota, and the hourly DM replies are counted per workspace.
Workspaces and API keys are created in the eksis app, not through the API. With several workspaces, store one key per workspace and pick the key that matches the channel.
Limits per workspace
These numbers come from the plan. Each plan's limits apply to one workspace.
| Pro Eksis | Super Eksis, each workspace | Builder Eksis | |
|---|---|---|---|
| Channels | 20 | 20 | The number paid for, 25 to 1,000 |
| REST and MCP requests a day | 1,000 | 10,000 | 1,000 for each channel paid for |
| DM replies an hour, through the API and MCP | 60 | 600 | 120 for each channel |
| DM replies an hour into one conversation | 20 | 20 | 20 |
| API keys | 3 | 3 | 3 |
| Webhook endpoints | 3 | 3 | 3 |
- Free has one key and 200 requests a day for the MCP server only. The REST API answers a Free key with
402, and Free has no direct messages and no webhooks. - Super Eksis is billed per workspace, from 5 workspaces. The numbers in its column apply to each workspace on its own: five Super Eksis workspaces hold up to 100 channels, 20 in each.
- Builder Eksis is billed per channel, from 25 channels, for one workspace that holds your customers' channels. The daily requests are one pool for the workspace: 100 channels paid for give 100,000 requests a day. DM replies are counted per channel, so a busy customer never uses up the replies of another, and
GET /v1/mereturnsdmRepliesScope: "channel". - Requests through the REST API and tool calls through MCP share the same daily quota.
- Current prices are on the pricing page. The workspace owner changes the plan under Settings, Plan and billing in the app. Plans and limits covers the rest of each plan.
Need more
When one workspace needs more channels, requests, or DM replies than its plan allows, write to support@eksis.io with the workspace and the numbers you need. eksis can raise the limits of a single workspace.
Read the limits from the API
GET /v1/me returns the workspace, the key, the limits that apply right now, and what the plan includes.
curl https://api.eksis.io/v1/me \
-H "Authorization: Bearer $EKSIS_API_KEY"limits.channels is the number of channels the workspace may hold. GET /v1/channels lists the ones it holds now, so the difference is how many customers can still connect. features says whether the plan includes restApi, directMessages, webhooks, and analytics. Details: Describe the key and its workspace.
Keys and roles
A workspace has up to 3 keys. Each key carries a role, and a key never gets more access than the person who created it. Give each part of your app the smallest role it needs:
| Work | Role it needs |
|---|---|
| Read channels, conversations, comments, and posts | viewer |
| Reply to DMs and comments, hide comments, schedule and publish posts | editor |
| Connect channels and manage webhook endpoints | admin |
A common split is an admin key used only by the code that connects channels and sets up webhooks, and an editor key for everything that runs on each message. See Roles and Authenticating.