Developer documentation
Build on Saltare.
Three surfaces for integrating with a workspace — pick the one that matches how your tool talks to the outside world.
REST API
JSON over HTTPS
List tasks, post messages, trigger agents, create documents. Bearer-token auth, workspace implied by the key.
MCP
Claude Desktop, Cursor, ChatGPT
Expose Saltare tools over the Model Context Protocol. Connect any MCP-aware agent host directly to a workspace.
Webhooks
Signed event delivery
Subscribe to task, message, and document events. HMAC-SHA256 signed, retried with backoff, delivered to any public URL.
Which one do I need?
- Building a Zap, n8n node, or Make automation?
- Use the REST API to poll or act, or subscribe to webhooks for push-style flows.
- Connecting Claude Desktop, Cursor, or an in-house MCP host?
- Use the MCP server. It reuses the same AI tools Saltare's own agents use.
- Giving an agent access to your own HTTP API?
- Import an OpenAPI 3.x spec as a Skill — every operation becomes a callable tool without writing code. No dedicated docs page yet; see the in-app Skills UI.
Get an API key
- Open your workspace and go to Settings → API Keys.
- Create a new key, pick the scopes you need, and optionally bind it to an agent.
- Copy the
sk_sal_…token shown once at creation — you won't see it again. - Send it as
Authorization: Bearer <token>on every request.