The API reference moved here from eksis.io/developers.

Introduction

What the eksis REST API does, where it lives, and what you need before the first call.

The eksis API lets your own code do what the eksis app does with a workspace: read the connected channels, bring in media, draft, schedule, and publish posts, answer comments and direct messages, and read analytics. Webhooks tell your server when something happens. It speaks JSON over HTTPS, and one key reaches one workspace.

Base URL

https://api.eksis.io/v1

Every endpoint lives under /v1. The full OpenAPI 3.1 document is at api.eksis.io/v1/openapi.json. These pages are built from that same document, so you can import it into Postman, Insomnia, or a client generator and get exactly what is described here.

What you need

  • A workspace on the Starter plan or higher. A key from a Free workspace is answered with 402 here. On Free, the key works with the MCP server only.
  • An API key. Open the workspace in the eksis app, go to API & MCP, and choose Create key. A key belongs to one workspace and is shown once, so copy it before you close the dialog.

Send the key in the Authorization header of every request:

Authorization: Bearer eksis_sk_...

Keep the key on your server

A key in a browser, an app bundle, or a repository can be read by anyone who opens them.

Concepts

Platforms and events

Endpoints

Each card opens the first endpoint of its group.

The quick start strings five of these together, from checking a key to a scheduled post.

AI assistants

Claude, ChatGPT, Cursor, and other assistants can do the same work through the eksis MCP server, on every plan. Setup steps for each client are in the MCP section.

On this page