---
title: "Get client allocation or deallocation"
method: GET
path: "/api/network/v1/enterprises/{enterpriseId}/clients/allocations/{allocationId}"
tags: ["Client Allocations & Deallocations"]
---

# Get client allocation or deallocation

`GET /api/network/v1/enterprises/{enterpriseId}/clients/allocations/{allocationId}`

Returns an allocation or deallocation. For use only by OES clients.

Error scenarios:
- 400: Invalid Request Error
- Occurs when the request parameters are invalid or incomplete.
- Examples: Invalid UUID format for allocationId, invalid enterpriseId format.

- 401: Authentication Error
- Occurs when the request is not authorized.
- Examples: Caller is not a member of the enterprise.

- 403: Permission Denied Error
- Occurs when the authenticated partner doesn't have access to the requested allocation
- Examples: Enterprise does not have OES license.

- 404: Not Found Error
- Occurs when the requested allocation does not exist for this client
- Examples: Allocation with specified ID doesn't exist, allocation exists but belongs to different client

- 500: Internal Server Error
- Occurs when there's an unexpected error processing the request
- Examples: Database connection failure, currency mapping error,
error transforming allocation data for response

**Requires access token scope:** `settlement_network_read`

## Path parameters

- `allocationId` string, required
- `enterpriseId` string, required

## Response `200`

OK

- V1AllocationGetPayload
  - `allocation` V1AllocationGetOutput, required
    - `id` string, required — The unique identifier of the allocation/deallocation. This is a UUID that uniquely identifies the allocation record.
    - `amount` union, required
      - PositiveCurrencyAmount
        - `currency` string, required
        - `quantity` string, required
      - PositiveBigNumberCurrencyAmount
        - `currency` string, required
        - `quantity` string, required
    - `connectionId` string, required — The unique identifier of the connection this allocation is for. This identifies a connection between a client and partner.
    - `clientExternalId` string, required — External identifier provided by the client when creating the allocation/deallocation. Used for idempotence and correlation with client systems.
    - `partnerExternalId` string — External identifier of the allocation/deallocation in the partner system. May be populated when partners provide their own identifier for the allocation.
    - `initiatedBy` string, required — The identifier of the user that initiated the allocation/deallocation. Represents the user ID from the BitGo platform.
    - `notes` string — Optional notes provided by the client when creating the allocation/deallocation. Can contain additional context or information about the purpose of the allocation.
    - `createdAt` string, date-time, required — The date and time when the allocation/deallocation was created. Represented as an ISO 8601 formatted date string.
    - `updatedAt` string, date-time, required — The date and time when the allocation/deallocation was last updated. Represented as an ISO 8601 formatted date string.
    - `retriable` boolean, required — Indicates whether or not the allocation/deallocation is retriable. When true, clients may retry the operation if it did not complete successfully. Retry can be performed by re-sending the same allocation request that was originally sent.
    - `evaluationId` string — The unique identifier of the policy evaluation for this allocation/deallocation. Present when policy evaluation was performed as part of the allocation flow.
    - `pendingApprovalId` string — The unique identifier of the pending approval for this allocation/deallocation. Present when policy evaluation resulted in a PENDING status requiring manual approval.
    - `policyResult` 'approved' | 'rejected' — The result of the policy evaluation for this allocation/deallocation. - 'approved': Policy evaluation passed and the operation was allowed - 'rejected': Policy evaluation failed and the operation was denied Not present if no policy evaluation was performed or if evaluation is still pending.
    - `reason` string, nullable, required — The reason that the allocation/deallocation is not cleared. Provides a descriptive explanation for why the allocation is in the reserved state. Will not be defined if the allocation is cleared.
    - `status` 'cleared' | 'released' | 'reserved', required
    - `type` 'allocation' | 'deallocation', required

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `500` — Internal Server Error

---

[API](https://skmtc.net/bitgo/apis/bitgo-api.md) · [All operations](https://skmtc.net/bitgo/apis/bitgo-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/bitgo/bitgo-api/revisions/e445c15e5bee/schema)