Skip to main content
PUT
Update 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.

Path Parameters

id
string
required

The ID of the custom service.

Body

application/json
name
string

The name of the custom service.

domain
string

The domain for branding/logo lookup.

scopedId
string | null

Rekeys the service's copy-invariant identity ("csvc_" + 22 alphanumerics). Omit to leave unchanged. Must be unique within the team.

Response

200 - application/json

Success

data
data · object

The updated custom service.