Skip to content

API reference

Remove voice binding

voice.RemoveVoiceBindingWriteMember delegation

Remove a capability from a phone assistant. The caller must have management permission for that assistant.

POST/v1/operations/voice.RemoveVoiceBinding
On this page

Access & visibility

Allow voice.RemoveVoiceBinding on your API key.

Acting member required. Send Brigg-Act-As with an approved member account ID. The key supplies permissions; the member selects whose data is used.

The selected member must be active and approved by the credential. This selects whose private data is used; the credential supplies permissions. Private ownership and project boundaries still apply.

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.

idstringRequired

Use id from bindings. Removing a binding does not delete the source capability. voice.GetVoiceCatalog.

At least 1 character.

Disconnect a capability

Find the binding in Get voice catalogue and pass its id. Removal disconnects that capability from the assistant; it does not delete the source app, meeting booking link or inbox. There is no offering revision or settings body to send.

The acting member needs management authority over the target inbox. For a personal assistant, only its owner can manage the binding. If the inbox has been deleted or its agent unassigned, a workspace manager can remove the orphaned binding. A binding already absent returns ok: true. Retry the original action with its original idempotency key.

Re-read the catalogue to confirm the remaining capabilities. Start voice test can check the assistant after the change.

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. Supply Brigg-Act-As with a member authorized by the key’s delegation grant. The selected member must be active and approved by the credential. This selects whose private data is used; the credential supplies permissions. Private ownership and project boundaries still apply.
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": {
    "id": {
      "type": "string",
      "minLength": 1,
      "description": "Use id from bindings. Removing a binding does not delete the source capability. [voice.GetVoiceCatalog](/reference/voice/GetVoiceCatalog)."
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "id": "vb_booking_support"
    }
  ]
}
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.