Skip to content

API reference

Set phone number usage

support.SetPhoneNumberUsageWriteAPI key

Record whether an inbox phone number is used directly as the support number or receives forwarded calls from an existing number.

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

Access & visibility

Allow support.SetPhoneNumberUsage on your API key.

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.

e164stringRequired

Use the existing number's e164 value including + and the country calling code. This operation does not rent a number. support.ListPhoneNumbers.

At least 3 characters.

usagestringRequired

Whether customers call this number directly or reach it through forwarding.

Allowed: "own_number", "forward".

Response

Returns 200 OK with a JSON body.

okbooleanRequired

Whether the action completed successfully.

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": {
    "e164": {
      "type": "string",
      "minLength": 3,
      "description": "Use the existing number's e164 value including + and the country calling code. This operation does not rent a number. [support.ListPhoneNumbers](/developers/reference/support/ListPhoneNumbers)."
    },
    "usage": {
      "type": "string",
      "enum": [
        "own_number",
        "forward"
      ],
      "description": "Whether customers call this number directly or reach it through forwarding."
    }
  },
  "required": [
    "e164",
    "usage"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "e164": "+4721001234",
      "usage": "own_number"
    }
  ]
}
Full response JSON schema
{
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean",
      "description": "Whether the action completed successfully."
    }
  },
  "required": [
    "ok"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "ok": true
    }
  ]
}

Search by operation name or what you want to build.

Use arrow keys to browse. Enter opens a result.