> ## Documentation Index
> Fetch the complete documentation index at: https://developers.fireblocks.com/llms.txt
> Use this file to discover all available pages before exploring further.

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://developers.fireblocks.com/feedback

```json
{
  "path": "/api-reference/compliance/add-vault-accounts-to-the-address-registry-opt-out-list",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# Add vault accounts to the address registry opt-out list

> Adds one or more vault account ids to the workspace opt-out list for the address registry.



## OpenAPI

````yaml https://docs.fireblocks.com/api/v1/swagger.yaml post /address_registry/vaults
openapi: 3.0.0
info:
  title: Fireblocks API
  description: >
    Fireblocks provides a suite of applications to manage digital asset
    operations and a complete development platform to build your business on the
    blockchain.


    - Visit our website for more information: [Fireblocks
    Website](https://fireblocks.com)

    - Visit our developer docs: [Fireblocks
    DevPortal](https://developers.fireblocks.com)
  version: 1.6.2
  contact:
    email: developers@fireblocks.com
servers:
  - url: https://api.fireblocks.io/v1
    description: Fireblocks Production Environment Base URL
  - url: https://sandbox-api.fireblocks.io/v1
    description: Fireblocks Sandbox Environment Base URL
security: []
paths:
  /address_registry/vaults:
    post:
      tags:
        - Compliance
      summary: Add vault accounts to the address registry opt-out list
      description: >-
        Adds one or more vault account ids to the workspace opt-out list for the
        address registry.
      operationId: addAddressRegistryVaultOptOuts
      parameters:
        - $ref: '#/components/parameters/X-Idempotency-Key'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/AddressRegistryAddVaultOptOutsRequest'
      responses:
        '200':
          description: Opt-outs recorded; response body includes `acceptedCount`.
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AddressRegistryAddVaultOptOutsResponse'
        '400':
          description: Validation error (e.g. empty list or invalid vault ids)
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AddressRegistryError'
        default:
          $ref: '#/components/responses/Error'
      x-codeSamples:
        - lang: TypeScript
          source: >-
            const response:
            Promise<FireblocksResponse<AddressRegistryAddVaultOptOutsResponse>>
            =
            fireblocks.compliance.addAddressRegistryVaultOptOuts(complianceApiAddAddressRegistryVaultOptOutsRequest);
        - lang: Java
          source: >-
            CompletableFuture<ApiResponse<AddressRegistryAddVaultOptOutsResponse>>
            response =
            fireblocks.compliance().addAddressRegistryVaultOptOuts(addressRegistryAddVaultOptOutsRequest,
            idempotencyKey);
        - lang: Python
          source: >-
            response =
            fireblocks.compliance.add_address_registry_vault_opt_outs(address_registry_add_vault_opt_outs_request,
            idempotency_key);
components:
  parameters:
    X-Idempotency-Key:
      name: Idempotency-Key
      in: header
      description: >-
        A unique identifier for the request. If the request is sent multiple
        times with the same idempotency key, the server will return the same
        response as the first request. The idempotency key is valid for 24
        hours.
      required: false
      schema:
        type: string
  schemas:
    AddressRegistryAddVaultOptOutsRequest:
      type: object
      properties:
        vaultAccountIds:
          type: array
          description: >
            Vault account ids to add to the opt-out list (non-empty). Each
            element may be a JSON number or a decimal string; both forms are
            accepted.
          minItems: 1
          items:
            oneOf:
              - type: integer
                format: int32
                example: 10001
              - type: string
                example: '10001'
          example:
            - 10001
            - '10002'
      required:
        - vaultAccountIds
    AddressRegistryAddVaultOptOutsResponse:
      type: object
      description: >-
        Result of adding vault account ids to the workspace opt-out list for the
        address registry.
      properties:
        acceptedCount:
          type: integer
          format: int32
          description: >-
            Number of vault ids from the request that were processed. An empty
            `vaultAccountIds` list is rejected with HTTP 400, not a 200 with
            zero.
          example: 3
      required:
        - acceptedCount
    AddressRegistryError:
      type: object
      description: Error body for address registry operations (4xx and 5xx).
      properties:
        code:
          type: integer
          description: >
            Application error code when present. For HTTP 400 on legal-entity
            lookup, distinguish: 4100 — request validation (e.g. missing, empty,
            or whitespace-only `address` after trim); 2140 — workspace not opted
            in to the address registry (`AR_OPT_IN_REQUIRED`). 2142 — not found
            (404). Other codes may appear, including on server errors.
          example: 2140
        message:
          type: string
          description: Human-readable error message
          example: Address registry opt-in required for this workspace.
      required:
        - message
    ErrorSchema:
      type: object
      properties:
        message:
          type: string
        code:
          type: number
  headers:
    X-Request-ID:
      schema:
        type: string
      description: >-
        Unique ID correlated to the API request. Please provide it in any
        support ticket you create or on Github issues related to Fireblocks SDKs
  responses:
    Error:
      description: Error Response
      headers:
        X-Request-ID:
          $ref: '#/components/headers/X-Request-ID'
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorSchema'

````