> For the complete documentation index, see [llms.txt](https://docs.neox.vn/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neox.vn/docs/global/global-collections/integration/virtual-accounts/get-virtual-account-request-records.md).

# Get Virtual Account Request Records

#### Endpoint: GET /v2/gc/virtual-accounts/{virtualAccountRequestId}/request-records

#### Description: Retrieve the history of all submitted requests associated with a virtual account application.

## Request

#### Request Body Field Descriptions (JSON)

| Field Name | Type | Required | Description                               |
| ---------- | ---- | -------- | ----------------------------------------- |
| N/A        | N/A  | N/A      | GET request does not require a JSON body. |

#### Request sample

```json
// No request body required for this GET endpoint.
```

### Response

#### Response Field Descriptions

| Field Name    | Type   | Description                            |
| ------------- | ------ | -------------------------------------- |
| code          | number | Response code.                         |
| state         | number | State of the response.                 |
| data          | object | Container for the request record list. |
| message       | string | Response message.                      |
| neoResponseId | string | Unique NeoX response identifier.       |

#### `docs` object item fields:

| Field Name              | Type        | Description                                                                         |
| ----------------------- | ----------- | ----------------------------------------------------------------------------------- |
| virtualAccountRequestId | string      | NeoX identifier for the virtual account application.                                |
| requestType             | string      | Type of operation submitted. Enum: `ADD`, `UPDATE`, `DELETE`.                       |
| requestId               | string      | Merchant-supplied `requestId` of the original request that created this record.     |
| status                  | string      | Status of this individual request. Enum: `INIT`, `PROCESSING`, `SUCCESS`, `FAILED`. |
| createDateTime          | date string | Timestamp when this request record was created (ISO 8601).                          |
| completeDateTime        | date string | Timestamp when this request was completed or failed (ISO 8601). Empty if pending.   |

#### Response sample

```json
{
  "code": 1,
  "state": 2,
  "data": {
    "docs": [
      {
        "virtualAccountRequestId": "VA-20240301-00012345",
        "requestType": "ADD",
        "requestId": "d4e5f6a7-8901-4b23-c456-789012345678",
        "status": "SUCCESS",
        "createDateTime": "2024-03-01T08:00:00Z",
        "completeDateTime": "2024-03-02T14:30:00Z"
      }
    ]
  },
  "message": "Successful",
  "neoResponseId": "f0a1b2c3-4567-4d89-e012-345678901234"
}
```

## Example cURL

```bash
curl -X GET "https://{base_url_openapi}/v2/gc/virtual-accounts/{virtualAccountRequestId}/request-records" \
  -H "Authorization: Bearer <YOUR_TOKEN>" \
  -H "Content-Type: application/json" \
  -H "Accept-Language: en"
```

### Notes

* Requires Bearer token in the Authorization header.
* The Accept-Language header can be used to specify the response language (Support: "vi", "en").
* No request body required.
* Replace `{virtualAccountRequestId}` with the actual virtual account request ID returned by the Create Virtual Account API.
* This endpoint is useful for auditing all historical requests (create, update, delete) submitted against a single virtual account application.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.neox.vn/docs/global/global-collections/integration/virtual-accounts/get-virtual-account-request-records.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.