Integrations overview
Connect your workspace to the tools your team already uses.
OpenAPI Studio plugs into the tools your team already uses. Each integration is connected per-workspace; once it’s set up, every member of the workspace benefits.
What’s available
| Integration | What it does |
|---|---|
| GitHub | Push your spec to a repo on demand; sync changes for code review. |
| Slack | Notifications on spec changes, recipe failures, breaking changes, member activity. |
| Linear | File issues straight from the editor. |
| Notion | Embed and update spec pages in your Notion workspace. |
| MCP — connect AI assistants | Expose your spec to Claude, Cursor, Continue, and other Model Context Protocol clients. |
How OAuth connections work
Each integration uses standard OAuth — you click Connect, sign in with the third-party tool, grant scopes, and the tokens are stored encrypted in your workspace. We never ask for raw API keys for the supported providers.
You can disconnect at any time. Disconnecting:
- Revokes the stored token immediately.
- Stops any scheduled notifications or syncs.
- Leaves any data already in the third-party tool intact.
Permissions
Workspace Owners can connect, configure, and disconnect integrations. Editors can use connected integrations (e.g. file a Linear issue) but can’t manage them. Viewers can’t trigger writes via integrations.
Privacy
OpenAPI Studio sends to integrations only what’s required for the action you’ve configured. For example, the Slack integration only posts the events you’ve toggled on; it doesn’t have access to your spec content unless you ask it to (e.g. a “spec change summary” notification).
Custom integrations
For tools we don’t support natively, hotlinks + recipes cover most of the gap:
- Hotlinks give any tool a stable URL to fetch your spec.
- Recipes can call any HTTP endpoint, so notifying a custom webhook is one step.
If you’d like a native integration for a specific tool, the support form on the dashboard collects requests.