---
title: "batch/details"
method: GET
path: "/batch/details"
tags: ["Batch Request Endpoints"]
---

# batch/details

`GET /batch/details`

This endpoint is used to fetch the details of a specific batch transaction request

## Query parameters

- `AccountID` string, required
- `Key` string, required
- `Signature` string, required
- `BatchTransactionRequestID` integer, required

## Response `200`

- object
  - `Success` boolean, required — True if the sending was successful, false if it failed
  - `ErrorMessage` string, required — Contains a description of the error if the request failed
  - `BatchDetails` object, required — Array serialized as a JSON object (JSON_FORCE_OBJECT): numeric string keys '0','1',... Array of objects. Each object contains the details of each transaction in the batch transaction request.
    - `0` object
      - `BatchTransactionRequestDetailsRecordID` integer, required — The unique ID of the batch transaction request detail
      - `TransactionPayload` object, required — JSON object of the submitted transaction
      - `TransactionID` integer, required — Unique ID of the created transaction, if applicable
      - `ScheduledTransactionID` integer, required — Unique ID of the created scheduled transaction, if applicable
      - `ELinxRequestID` integer, required — Unique ID of the created eLinx request, if applicable
      - `FailureReason` string, required — Reason the transaction failed to create, if applicable
      - `Status` string, required — Status of the transaction. Possible values are: submitted, created

---

[API](https://skmtc.net/vopay/apis/accounts.md) · [All operations](https://skmtc.net/vopay/apis/accounts/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/vopay/accounts/versions/7033bd231ec7/schema)