Skip to main content
Any agent that can make an HTTP request can use this API. It needs an API key and the OpenAPI spec, which describes every endpoint, parameter, minimum role and whether a call is destructive.

​
What to give your agent

​
Give an agent the least power it needs

The key runs with its creator’s role. For an agent that only reads (reporting, inbox summaries), create the key as a user with the view role. It then can’t launch campaigns or send replies, even by mistake.

​
Make it ask before destructive calls

Every operation in the spec has x-destructive. Calls marked true send real email or delete things (for example launching a campaign, replying to a thread, deleting a mailbox). Tell your agent to confirm with you first:

​
n8n, Make and Zapier

Use the HTTP Request node or step with the base URL above and an X-API-Key header stored as a credential. Writes take a JSON body (or a file upload for CSV leads), as shown on each endpoint’s page.

​
Docs MCP server

These docs have their own MCP server at https://docs.salessequencer.com/mcp. Connect it and your coding agent can search these docs while it writes your integration. It searches the docs only; it doesn’t call the API.
In Claude, Cursor or VS Code, add it as a custom MCP server with the same URL.

​
Read these docs from your agent

Every page here is also available as Markdown. Add .md to any page URL, or point your agent at /llms.txt for the whole list. The menu at the top of each page can copy it or open it in ChatGPT or Claude.