A shared inbox API for reading and writing conversations from your own software
The Sektra API gives your own software the same view of the shared inbox that a teammate has in the app. It reads conversations, messages, contacts, tags, inboxes and teammates, and it writes replies, new emails, notes, tags, assignment, status and contacts. Developers use it to build internal tools and to copy inbox activity into a CRM or a reporting database. It is a REST API that exchanges JSON over https, with keys created in settings and a published reference.
What Sektra does with the public API
What the API can read
A key can list conversations by inbox, status, owner or recent activity, and fetch one conversation with its tags, participants and owner. Messages come with their full bodies in HTML and text, their senders and recipients, and their attachment details. The API also lists contacts, the inboxes the key can reach, the tags in those inboxes and the teammates in the account.
What the API can write
With write access a key can send a new email from an inbox, reply to a conversation, and add an internal note. It can add or remove a tag, assign or unassign a conversation, close, reopen or snooze it, and create or update a contact. Each write runs through the same path as the app, so permissions are checked, teammates see the change at once, and rules and webhooks fire as usual.
API keys and permissions
Keys are created under Settings, then API and webhooks, as read only or read and write, and each one is shown once. A key acts as the person who created it and reaches only the inboxes that person can see, so access follows the permissions the team already uses. A key can be revoked at any moment, and an account can hold up to 25 live keys.
Rate limit, paging and errors
Each key may make 600 requests a minute, and a request over the limit gets a 429 answer that says how long to wait. Lists are paged with a cursor, 25 items at a time by default and up to 100, or 20 for messages with their bodies. Errors share one shape, a code and a message, so client code can handle them in one place.
API reference
The reference is an OpenAPI document that the API serves itself and the settings page links to. It describes every endpoint with its parameters and responses, and it loads into any tool that reads OpenAPI. The same document describes the webhook deliveries, so a team building both sides works from one source.
Common questions
Setup, permissions and what Sektra reads from the public API, with a contact link for anything not covered here.
Does Sektra have an API?
Yes. Sektra has a REST API that reads and writes conversations, messages, notes, tags, assignment, status and contacts. It authenticates with a key created in settings, allows 600 requests a minute for each key, and is described in an OpenAPI document.
How does authentication work in the Sektra API?
Each request sends a key in the Authorization header, in the form Bearer followed by the key. A key carries the permissions of the person who created it, and it stops working if it is revoked or if that person leaves the account.
What is the Sektra API rate limit?
Each key may make 600 requests a minute, and the limit is counted for each key separately. A request over the limit receives a 429 answer with a Retry-After header that says how long to wait.
Can the API send email from a shared inbox?
Yes. A key with write access can start a conversation by sending a new email from an inbox, and it can reply inside an existing conversation. The message leaves from the inbox's own address in the same way as one written in the app, and an Idempotency-Key header keeps a retried request from sending twice.
Connect the public API and see it work
Connect a mailbox first, then add the public API from Settings. Both steps take a few minutes, and the team can work from the inbox the same day.