Skip to content

API reference

Create inbox

support.CreateInboxWriteAPI key

Create a team inbox with its forwarding email address and web chat channel. Returns the inbox ID, URL slug and forwarding address.

POST/v1/operations/support.CreateInbox
On this page

Access & visibility

Allow support.CreateInbox on your API key. Resource write permissions: core:Inbox.

Workspace access by default. Private member data requires approved member delegation through Brigg-Act-As; the key supplies permissions while private ownership and project boundaries remain enforced.

Set up authentication · Choose permissions

Request fields

Send a JSON object with the following fields. Required fields must be included; omit optional fields you do not need.

namestringRequired

Team inbox name, for example Customer support or Billing. Brigg derives its slug and forwarding address from this name.

At least 1 character. At most 80 characters.

Response

Returns 200 OK with a JSON body.

idstringRequired

Unique identifier. Use the value returned by a create or list operation.

slugstringRequired

Stable URL segment identifying this item.

namestringRequired

Display name.

forward_addressstring or nullRequired

The inbox's inbound address; null until the org holds a chat token.

Errors & retries

Set BRIGG_REQUEST_ID once for each logical action. The samples send it as Idempotency-Key. Reuse the same value and body on retries, including after a timeout; a missing response does not prove the action failed.

For rate limits, follow the server’s retry guidance and back off. See HTTP errors and safe retries and limits.

HTTP status Code What to do
400 invalid_json Send a JSON object with Content-Type: application/json.
400 invalid_input Check the request fields and types. Supply a stable Idempotency-Key containing 1–200 characters.
401 invalid_key The workspace API key is missing, invalid or revoked.
403 forbidden Check the key’s operation and resource grants. If Brigg-Act-As is supplied, the key must be authorized to delegate to that member.
404 not_found The requested operation or resource is not available to this credential.
429 rate_limited Wait for Retry-After before retrying. Reuse the original Idempotency-Key.

Next steps

Download OpenAPI · Versioning & retirement

JSON schemas

Use the complete schemas for validation or client generation.

Full request JSON schema
{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1,
      "maxLength": 80,
      "description": "Team inbox name, for example Customer support or Billing. Brigg derives its slug and forwarding address from this name."
    }
  },
  "required": [
    "name"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "name": "Customer support"
    }
  ]
}
Full response JSON schema
{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Unique identifier. Use the value returned by a create or list operation."
    },
    "slug": {
      "type": "string",
      "description": "Stable URL segment identifying this item."
    },
    "name": {
      "type": "string",
      "description": "Display name."
    },
    "forward_address": {
      "type": [
        "string",
        "null"
      ],
      "description": "The inbox's inbound address; null until the org holds a chat token."
    }
  },
  "required": [
    "id",
    "slug",
    "name",
    "forward_address"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "id": "e_example",
      "slug": "support",
      "name": "Customer support",
      "forward_address": "support@example.com"
    }
  ]
}

Search by operation name or what you want to build.

Use arrow keys to browse. Enter opens a result.