> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/classic-tokenization/use-cases/synchronize-tokens-using-batch-files/output-batch-file-structure.md).
# Output batch file structure
## Output batch file structure
The output file has a similar structure to the input batch file.
The output file structure is as follows:
| NAME | TYPE | SIZE | M/O/C | DESCRIPTION |
| -------------- | ------ | ---- | ----- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| header | Object | - | M | Summary of token synchronization results. |
| recordsResults | Array | - | C | An array of records.
Each record contains the result of the operation. This field may not be present if a file-level error occurs.
|
### Header
The header has the following structure:
| NAME | TYPE | SIZE | M/O/C | DESCRIPTION |
| ------------ | ------- | ---- | ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| batchId | String | 48 | M | Identifier from the input file batch header. |
| seqNumber | String | 48 | M | Sequence number from the input file batch header. |
| issuerId | String | 48 | M | Issuer identifier from the input file batch header. |
| operation | String | 48 | M | Operation from the input file batch header. |
| totalRecords | Integer | N/A | M | Total number of records included in the report. |
| errorCode | String | 3 | C | Present only when a file-level error occurs. See [Error codes](/classic-tokenization/use-cases/synchronize-tokens-using-batch-files/error-codes-table.md). |
### Record results
Each record has the following structure:
| NAME | TYPE | SIZE | M/O/C | DESCRIPTION |
| ----------------------------- | ------- | ---- | ----- | --------------------------------------- |
| rowId | Integer | - | M | Value provided in the input batch file. |
| virtualCardRegistrationResult | Object | - | M | |
#### Virtual card registration result
| NAME | TYPE | SIZE | M/O/C | DESCRIPTION |
| --------- | ------------- | ---- | ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| status | String | 2 | M | - OK (Batch registration completes successfully.)
- KO (Batch registration fails.)
|
| card | Card (Object) | N/A | M | Object containing the card identification data and the result. |
| errorCode | String | 3 | C | Error code returned when `status` is `KO`. See [Error codes](/classic-tokenization/use-cases/synchronize-tokens-using-batch-files/error-codes-table.md). |
**Card**
| NAME | TYPE | SIZE | M/O/C | DESCRIPTION |
| -------------- | --------------- | ------ | ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| id | String | 1...48 | M | Unique identifier assigned by the Issuer. |
| status | String | 2 | M | - OK (Card record registration completes successfully.)
- KO (Card record registration fails.)
|
| virtualCardIds | Array of String | N/A | O | List of virtual card IDs that TIG registers for the card. |
| errorCode | String | 3 | C | Error code returned when `status` is `KO`. See [Error codes](/classic-tokenization/use-cases/synchronize-tokens-using-batch-files/error-codes-table.md). |
### Batch file example
```json
{"header":
{
"batchId":"0000000000001111111111FF",
"seqNumber":"001",
"operation":"VIRTUAL_CARD_REGISTRATION",
"issuerId":"BANK_PQRST",
"totalRecords":1
},
"recordsResults":
[
{"rowId":0,
"virtualCardRegistrationResult":{
"card": {
"id":"cms_f71b83a3-75da-4056-82a6-2d6128555463",
"status":"OK",
"virtualCardIds":["c05f9cf0-40f9-11ee-a782-af4a746b","c05f75e1-40f9-11ee-9761-af4a746b"],
}
}
]
}
```
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.payments.thalescloud.io/classic-tokenization/use-cases/synchronize-tokens-using-batch-files/output-batch-file-structure.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.