> 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/es/casos-de-uso/sincroniza-tokens-usando-archivos-por-lotes/esquema-json-del-archivo-por-lotes.md).
# Esquema JSON del archivo por lotes
Use estas definiciones de JSON Schema para validar archivos por lotes utilizados para la sincronización de tokens.
Para una referencia de campos legible por humanos y ejemplos, vea:
* [Estructura del archivo por lotes](/classic-tokenization/es/casos-de-uso/sincroniza-tokens-usando-archivos-por-lotes/estructura-del-archivo-por-lotes.md)
* [Estructura del archivo de resultados por lotes](/classic-tokenization/es/casos-de-uso/sincroniza-tokens-usando-archivos-por-lotes/estructura-del-archivo-de-salida-por-lotes.md)
* [Tabla de códigos de error](/classic-tokenization/es/casos-de-uso/sincroniza-tokens-usando-archivos-por-lotes/tabla-de-codigos-de-error.md)
{% hint style="info" %}
Estos esquemas apuntan a JSON Schema draft 2020-12.
Algunos validadores pueden tratar la `nullable` palabra clave como no estándar. Valide con las herramientas que use en su backend emisor.
{% endhint %}
### Esquema de archivo de entrada por lotes
#### Registro de tarjeta virtual
Use este esquema para validar un archivo de entrada donde:
* `header.operation` es `VIRTUAL_CARD_REGISTRATION`.
* Cada registro contiene `rowId` y `virtualCardRegistrationRequest.card`.
* `firma` es un JWS desacoplado (ver [Estructura del archivo por lotes](/classic-tokenization/es/casos-de-uso/sincroniza-tokens-usando-archivos-por-lotes/estructura-del-archivo-por-lotes.md)).
{% code title="input-virtual-card-registration.schema.json" %}
```json
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"header": {
"type": "object",
"properties": {
"batchId": { "type": "string", "nullable": false },
"seqNumber": { "type": "string", "nullable": false },
"operation": {
"type": "string",
"enum": ["VIRTUAL_CARD_REGISTRATION"]
},
"issuerId": {
"type": "string"
}
},
"additionalProperties": false,
"required": [
"batchId",
"seqNumber",
"operation",
"issuerId"
]
},
"records": {
"type": "array",
"items": {
"type": "object",
"properties": {
"rowId": {
"type": "integer"
},
"virtualCardRegistrationRequest": {
"type": "object",
"properties": {
"card": {
"type": "object",
"required": ["id", "scheme", "encryptedData"],
"properties": {
"id": { "type": "string", "nullable": false },
"scheme": { "type": "string", "enum": ["MASTERCARD", "VISA"] },
"encryptedData": { "type": "string" }
}
}
},
"required": ["card"],
"additionalProperties": false
}
},
"required": [
"rowId",
"virtualCardRegistrationRequest"
]
},
"additionalItems": false
},
"signature": { "type": "string", "nullable": false, "minLength": 1 }
},
"additionalProperties": false,
"required": [
"header",
"records",
"signature"
]
}
```
{% endcode %}
### Esquema de archivo de resultados por lotes
#### Resultado del registro de tarjeta virtual
Use este esquema para validar el archivo de resultados de salida producido después de procesar un archivo por lotes de entrada.
{% code title="output-virtual-card-registration.schema.json" %}
```json
{
"type": "object",
"properties": {
"header": {
"type": "object",
"properties": {
"batchId": { "type": "string" },
"seqNumber": { "type": "string" },
"operation": { "type": "string", "enum": ["VIRTUAL_CARD_REGISTRATION"] },
"issuerId": { "type": "string", "minLength": 10, "maxLength": 10 },
"errorCode": { "type": "string" },
"totalRecords": { "type": "integer" }
},
"additionalProperties": false
},
"recordsResults": {
"type": "array",
"items": [
{
"type": "object",
"properties": {
"rowId": {
"type": "integer"
},
"virtualCardRegistrationResult": {
"type": "object",
"properties": {
"card": {
"type": "object",
"properties": {
"id": { "type": "string" },
"status": { "type": "string" },
"digitalCardIds": {
"type": "array",
"items": [
{
"type": "string"
}
]
}
"errorCode": { "type": "string" }
},
"required": ["id", "status"],
"additionalProperties": false
},
"errorCode": { "type": "string" },
"status": { "type": "string" }
},
"required": ["card"],
"additionalProperties": false
}
},
"required": ["rowId", "virtualCardRegistrationResult"]
}
]
}
},
"required": ["header"],
"additionalProperties": false
}
```
{% endcode %}
---
# 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/es/casos-de-uso/sincroniza-tokens-usando-archivos-por-lotes/esquema-json-del-archivo-por-lotes.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.