Skip to main content

​
Overview

Organizations group connections, members and billing for a team or a client. On the API, organizations aren’t managed through a public CRUD endpoint — instead, your API key’s scope determines which organization’s data you see, and every request is filtered automatically.
Creating organizations, inviting members and changing roles is done in the dashboard (or the internal app API), not the public /v1 API. See Managing members and Permissions.

​
How Scoping Works

There are two kinds of keys (see Authentication):

Personal key

Sees your own connections plus connections in every organization you’re a member of.

Organization key

Bound to a single organization — only ever sees that organization’s connections and data.
You never pass an organization ID to “switch” context. The key decides what’s visible, so an organization key is the safest way to give a client, a CI job, or a per-tenant integration access to exactly one organization.

​
Filtering by Organization

When a personal key can see multiple organizations, several endpoints accept an organization_id filter to narrow results to one of them:
The organization each connection belongs to is included in Connections API responses:

​
Creating Connections in an Organization

When creating a connection, set organization_id to place it in an organization you belong to (omit it, or use "personal", for a personal connection):
You must have the member, admin or owner role in that organization, or the request returns 403. An organization-scoped key can only ever create in its own organization.

​
Managing Organizations & Members

Creating organizations

Set up a new organization for a team or client

Managing members

Invite, remove and re-role teammates

Permissions

What each role can do

Authentication

Personal vs. organization API keys