Skip to main content
POST
Create Custom Service

Authentication and permissions

Token requirements: User-based token (OAuth) or Organization-scoped API key or Team-scoped API key. Send a bearer access token for one of these identities. The permissions and resource restrictions below also apply.
Permissions joined by + are all required; or separates alternatives. Full-access keys still cannot call endpoints marked unsupported. Team keys must allow every team checked by the request. OAuth access depends on the user’s roles and resource access.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
teamId
string
required

The ID of the team.

name
string
required

The name of the custom service (e.g., "Internal HR System").

domain
string

The domain for branding/logo lookup (e.g., "hr.company.com").

scopedId
string | null

Copy-invariant identity to create the service under ("csvc_" + 22 alphanumerics). Leave unset and the server mints one. Set it to the source service's scoped_id when pushing configuration between teams or environments: the copy then answers to the same scoped id as its source, so the next push resolves it and updates in place instead of creating a duplicate. Must not already be in use on the team.

Response

200 - application/json

Success

data
data · object

The created custom service.