Create a company group
Needs the groups area at manage and the app's plan to include Enterprise SSO (402).
POST/api/v1/public/workspaces/workspaceId/enterprise/groups
- Sign-in
- A signed-in user's session: send the session id in the x-session-id header.
- Rate limit
- Up to 500 requests every 3 seconds per IP address; up to 1,000 requests a minute per API key (some requests are not counted); up to 60 requests a minute per signedInWriteKey (some requests are not counted).
Needs the groups area at manage and the app's plan to include Enterprise SSO (402). A group that reaches a company role also needs a recent sign-in (403 reauth_required). 409 name_taken, 422 too_many_groups, 403 managed_by_app.
Request
Path parameters
| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
workspaceId | string | Yes | - | - |
Send the body as application/json. The body is optional.
Body
| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
name | string | No | 1 to 60 characters | - |
description | string | No | at most 280 characters | - |
members | array of string | No | at most 1000 items | - |
linked | array of object | No | at most 6 items | - |
linked[].source | string | No | one of "workos_role", "directory", "sso_role", "sso_group" | - |
linked[].groupId | string | No | 1 to 200 characters | - |
linked[].groupName | string | No | at most 200 characters | - |
workspaces | array of object | No | at most 20 items | - |
workspaces[].workspaceId | string | No | matches ^[a-f0-9]{24}$ | - |
workspaces[].role | string | No | 1 to 64 characters | - |
companyRole | one of: string, null | No | - | - |
assignableInWorkOS | boolean | No | - | - |
includes | array of string | No | at most 50 items | - |
Example request
Replace each YOUR_... value with your own, and set the credential in the environment variable the sample reads.
curl -X POST "https://api.console.buildbase.app/api/v1/public/workspaces/YOUR_WORKSPACE_ID/enterprise/groups" \
-H "x-session-id: $BUILDBASE_SESSION_ID" \
-H "Content-Type: application/json" \
-d '{
"name": "Example",
"description": "string",
"members": [
"string"
]
}'const response = await fetch(
'https://api.console.buildbase.app/api/v1/public/workspaces/YOUR_WORKSPACE_ID/enterprise/groups',
{
method: 'POST',
headers: {
'x-session-id': process.env.BUILDBASE_SESSION_ID ?? '',
'Content-Type': 'application/json',
},
body: JSON.stringify({
name: 'Example',
description: 'string',
members: ['string'],
}),
}
);
if (!response.ok) {
throw new Error(`${response.status}: ${await response.text()}`);
}
const data = await response.json();import os
import requests
response = requests.post(
"https://api.console.buildbase.app/api/v1/public/workspaces/YOUR_WORKSPACE_ID/enterprise/groups",
headers={
"x-session-id": os.environ["BUILDBASE_SESSION_ID"],
},
json={
"name": "Example",
"description": "string",
"members": [
"string",
],
},
timeout=30,
)
response.raise_for_status()
data = response.json()Responses
200 OK
OK
{
"applied": 2,
"group": {
"companyRole": null,
"createdAt": "2026-01-01T00:00:00.000Z",
"createdVia": "app",
"description": "",
"groupId": "000000000000000000000001",
"includedIn": [],
"includes": [],
"inherited": [],
"linked": [
{
"groupId": "directory_group_01STUB5AFD616E105DFD330795",
"groupName": "backend-eng",
"source": "directory"
}
],
"managers": [],
"members": [
{
"email": "[email protected]",
"name": "Session User m23-nested-priya",
"userId": "000000000000000000000002"
}
],
"name": "Backend",
"people": 2,
"peopleBy": {
"included": 0,
"linked": 1,
"named": 1
},
"rolesReached": [],
"workos": null,
"workspaces": [
{
"role": "viewer",
"workspaceId": "000000000000000000000003",
"workspaceName": "Globex support 1767225600000"
}
]
},
"pending": 0
}Any other status
Any other answer the handler sends itself (its own refusals). Not described yet.
Errors
Each refusal, what it means, and what to do. The request changed nothing.
400 Bad Request
What it means: The request failed a validate() schema, or an id in the path is not a valid id. path names the field.
What to do: Fix the field the body names in path (or read message) and send the request again. Nothing was changed.
{
"error": true,
"success": false,
"path": "string",
"message": "string"
}401 Unauthorized
What it means: The credential is missing, expired or not accepted here, or the caller's role has no grant for x-permission (refused with 401 too). The body is the plain text Unauthorized, or a JSON body with a code where the gate says why.
What to do: Send the credential this operation asks for (see Sign-in above), or sign in again if it expired. A valid credential is also refused when the role has no grant for the permission above.
Unauthorized429 Too Many Requests
What it means: A rate limit in x-rateLimit was reached. retryAfter and the Retry-After header say how many seconds until the window resets.
What to do: Wait the number of seconds in the Retry-After header (also retryAfter in the body), then retry. Slow down repeated calls.
{
"success": false,
"message": "string",
"reason": "rate_limited",
"retryAfter": 1
}Events
A successful call can send these webhook events to the endpoints that subscribe to them:
Related
- Workspaces guide: how this part of BuildBase works
- All Workspaces operations
- API reference: every operation, by tag
- Sign-in and credentials for the HTTP API
- How the HTTP API reports errors
- Make your first call
- Error codes: every
codethe API returns - OpenAPI: operation
workspaces.enterprise.groups.createin public-v1.json