GET
/v2/beneficiary/{beneficiaryID}Get Beneficiary Details
Returns full details for a single beneficiary, including available payment types and linked payment instrument IDs.
Path variables
| Field | Type | Required | Possible values | Description |
|---|---|---|---|---|
beneficiaryID | string | Required | {beneficiaryID} | Unique beneficiary ID returned from Create Beneficiary or List Beneficiaries. |
Headers
| Field | Type | Required | Possible values | Description |
|---|---|---|---|---|
Authorization | string | Required | Bearer {SessionToken} | Session token from Get Session Token, sent as `Authorization: Bearer {SessionToken}`. Replace with the value from the `x-refresh-token` response header when present (typically within 2 minutes of expiry). Secured calls must use the same IP as the auth request. |
Response
| Field | Type | Possible values | Description |
|---|---|---|---|
ResponseCode | integer | 200 | 201 | 204 | 400 | 401 | 403 | 404 | 410 | 422 | 500 | 301 | 503 | 422 | API result code in the response envelope. Indicates success or the error category (e.g. 200 success, 400 bad request, 401 unauthorized). |
ResponseMessage | string | Success | Created | NoContent | BadRequest | Unauthorized | Forbidden | NotFound | Gone | UnprocessableContent | ServerError | ResourceMoved | ServiceUnAvailable | UnProcessableEntity | Human-readable label paired with ResponseCode (e.g. Success, BadRequest, Unauthorized). Use with ResponseCode to interpret the outcome. |
ResponseData | object | Please refer to below example for response body | Beneficiary profile, status, address, and available payment types. |
Example response
{
"ResponseCode": 200,
"ResponseMessage": "Success",
"ResponseData": {
"CreatedBy": "Rishav_Business - Rishav",
"CreatedOn": "2022-12-19T07:30:20.802-04:00",
"BeneficiaryId": "9005964837635141461",
"Available_Payments_Type": [
{
"label": "Withdraw (ETH)",
"value": "BUS_ETH_Account.Payment_ETH",
"PaymentInstrumentIDs": [
…Requires `Authorization: Bearer {SessionToken}` from Get Session Token. Refresh via `x-refresh-token` when supplied; use the same client IP as authentication.