Create Service Key

POST /service-keys

The only response in the API that carries a key. It is stored nowhere.

Role floor

Requires admin or above. The floor is a minimum, not a grant: scope filtering still applies on top of it, and a resource in another tenant answers 404 rather than 403.

Request body — ServiceKeyCreate

Field	Type		Notes
name	string	required	min length 1 max length 120
role	viewer | member | admin | owner | operator	optional	Default "member".
scope	workspace | organization | platform	optional	Default "workspace".
expires_at	string (date-time) | null	optional	—
request_timeout_s	integer | null	optional	min 1 max 3600

Responses

Status	Description	Body
201	Successful Response	ServiceKeyWithSecret
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

The body shows the fields the schema always carries. Which combination is legal is a service rule the schema cannot express, so read the description above before copying this.

curl -X POST https://your-deployment.example.com/service-keys \
  -H "Authorization: Bearer $COBRE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
       "name": "string"
     }'

Response — ServiceKeyWithSecret

Field	Type		Notes
key	string	required	—
service_key	ServiceKeyView	required	—