Get client allocation or deallocation
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 Params
-
allocationIdstring requiredThe unique identifier of the allocation to retrieve. This is a UUID that uniquely identifies the allocation record. -
enterpriseIdstring requiredThe enterprise identifier of the client. This identifies the client enterprise that owns the allocation.
Responses
200
OK
Response Body
object
-
allocationobject requiredallocation object
-
idstring requiredThe unique identifier of the allocation/deallocation. This is a UUID that uniquely identifies the allocation record. -
amountobject requiredThe amount of the allocation/deallocation. Contains both the currency identifier and the quantity in base units.ONE OF
-
currencystring required -
quantitystring required
-
currencystring required -
quantitystring required
-
-
connectionIdstring requiredThe unique identifier of the connection this allocation is for. This identifies a connection between a client and partner. -
clientExternalIdstring requiredExternal identifier provided by the client when creating the allocation/deallocation. Used for idempotence and correlation with client systems. -
partnerExternalIdstringExternal identifier of the allocation/deallocation in the partner system. May be populated when partners provide their own identifier for the allocation. -
initiatedBystring requiredThe identifier of the user that initiated the allocation/deallocation. Represents the user ID from the BitGo platform. -
notesstringOptional notes provided by the client when creating the allocation/deallocation. Can contain additional context or information about the purpose of the allocation. -
createdAtstring date-time requiredThe date and time when the allocation/deallocation was created. Represented as an ISO 8601 formatted date string. -
updatedAtstring date-time requiredThe date and time when the allocation/deallocation was last updated. Represented as an ISO 8601 formatted date string. -
retriableboolean requiredIndicates 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. -
evaluationIdstringThe unique identifier of the policy evaluation for this allocation/deallocation. Present when policy evaluation was performed as part of the allocation flow. -
pendingApprovalIdstringThe unique identifier of the pending approval for this allocation/deallocation. Present when policy evaluation resulted in a PENDING status requiring manual approval. -
policyResultstring enumThe 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.
approvedrejected -
reasonstring nullable requiredThe 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. -
statusstring enum requiredStatus of the allocation/deallocation.
Possible values:
- reserved: The amount for allocation/deallocation is reserved but operation has not completed. This is a temporary state awaiting final resolution.
- cleared: Terminal state; the amount for allocation/deallocation is cleared and funds have been successfully allocated. This indicates a successful operation.
- released: Terminal state; the amount for allocation/deallocation is released and funds have been returned. This indicates the operation failed, either because balance was insufficient for allocation/deallocation, or that the partner rejected the request to allocate/deallocate.
clearedreleasedreserved -
typestring enum requiredThe type of the entity.
Possible values:
- allocation: Represents an allocation of funds to a connection. This moves funds from a client's BitGo account to make them available for the specified connection.
- deallocation: Represents a deallocation of funds from a connection. This moves funds from a connection back to the client's BitGo account.
allocationdeallocation
-
401
Unauthorized
Response Body
object
-
errorstring required
403
Forbidden
Response Body
object
-
errorstring required
404
Not Found
Response Body
object
-
errorstring required
500
Internal Server Error
Response Body
object
-
errorstring required