> ## Documentation Index > Fetch the complete documentation index at: https://docs.compute.prentis.ai/llms.txt > Use this file to discover all available pages before exploring further. # Validate an upload > Step three, once the PUT has finished. Validation runs in the background: this returns straight away in state DATASET_STATE_VALIDATING. It checks that the file is JSON Lines -- UTF-8, one JSON object per line, no line over 8 MiB -- not that the rows have the shape a particular kind of training needs; that is checked when a job starts. ## OpenAPI ````yaml openapi/prentis-training.openapi.yaml POST /accounts/{account}/datasets/{dataset}:validateUpload openapi: 3.1.0 info: title: Prentis Training API version: 0.1.0 summary: >- Fine-tune models on your own data, with the same API key you use for inference. description: > Upload a dataset, start a fine-tuning job on it, and watch it train -- from code, with the API key you already use for inference. The jobs and datasets are the same ones the console shows: anything started here appears there, and the other way round. Every path is under `/v1/accounts/{account}`, where `{account}` is the account the key belongs to. A key reaches its own account only. A finished job produces a model in your account (`accounts/{account}/models/{outputModelId}`), listed under Custom models in the console. To call it, deploy it on a dedicated deployment and send inference requests to the deployment (`accounts/{account}/deployments/{deployment}`). servers: - url: https://compute.prentis.ai/v1 description: Production security: - bearerAuth: [] tags: - name: training - name: datasets paths: /accounts/{account}/datasets/{dataset}:validateUpload: post: tags: - datasets summary: Validate an upload description: >- Step three, once the PUT has finished. Validation runs in the background: this returns straight away in state DATASET_STATE_VALIDATING. It checks that the file is JSON Lines -- UTF-8, one JSON object per line, no line over 8 MiB -- not that the rows have the shape a particular kind of training needs; that is checked when a job starts. operationId: validateDatasetUpload parameters: - $ref: '#/components/parameters/Account' - $ref: '#/components/parameters/Dataset' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/ValidateUploadRequest' responses: '200': headers: x-request-id: $ref: '#/components/headers/x-request-id' content: application/json: schema: $ref: '#/components/schemas/Dataset' example: name: accounts/my-account/datasets/support-chats datasetId: support-chats displayName: Support chats state: DATASET_STATE_VALIDATING latestVersionNo: 1 createTime: '2026-10-10T07:40:00Z' updateTime: '2026-10-10T07:41:02Z' description: OK. '400': $ref: '#/components/responses/Error400' '401': $ref: '#/components/responses/Error401' '403': $ref: '#/components/responses/Error403' '404': $ref: '#/components/responses/Error404' '500': $ref: '#/components/responses/Error500' '503': $ref: '#/components/responses/Error503' x-codeSamples: - lang: curl label: cURL source: >- curl https://compute.prentis.ai/v1/accounts/my-account/datasets/support-chats:validateUpload \ -H "Authorization: Bearer $PRENTIS_API_KEY" \ -H "Content-Type: application/json" \ -d '{"uploadSession": "accounts/my-account/uploadSessions/01K7AWZ8C4E6G8J0L2N4Q6S8U0"}' components: parameters: Account: name: account in: path required: true schema: type: string maxLength: 64 description: >- Your account id -- the one in the console's address bar (my-account for this key). It must be the account the key belongs to. Dataset: name: dataset in: path required: true schema: type: string maxLength: 64 description: The dataset's id, as chosen when it was created. schemas: ValidateUploadRequest: type: object required: - uploadSession properties: uploadSession: type: string description: The uploadSession.name from the getUploadEndpoint response. Dataset: type: object properties: name: type: string datasetId: type: string displayName: type: string source: type: string enum: - DATASET_SOURCE_UPLOAD - DATASET_SOURCE_JOB_OUTPUT - DATASET_SOURCE_SPLIT sourceJob: type: string parentVersion: type: string state: type: string enum: - DATASET_STATE_CREATING - DATASET_STATE_UPLOADING - DATASET_STATE_VALIDATING - DATASET_STATE_READY - DATASET_STATE_FAILED - DATASET_STATE_DELETED latestVersionNo: type: integer totalBytes: type: string format: int64 activeReferenceCount: type: integer createdBy: type: string createTime: type: string format: date-time updateTime: type: string format: date-time deleteTime: type: string format: date-time versions: type: array items: $ref: '#/components/schemas/DatasetVersion' lineage: $ref: '#/components/schemas/DatasetLineage' DatasetVersion: type: object properties: name: type: string versionId: type: string versionNo: type: integer bytes: type: string format: int64 exampleCount: type: string format: int64 estimatedTokenCount: type: string format: int64 checksum: type: string state: type: string enum: - DATASET_VERSION_STATE_UPLOADING - DATASET_VERSION_STATE_VALIDATING - DATASET_VERSION_STATE_READY - DATASET_VERSION_STATE_FAILED validation: $ref: '#/components/schemas/DatasetValidation' createTime: type: string format: date-time topLevelKeys: type: array items: type: string DatasetLineage: type: object properties: consumers: type: array items: $ref: '#/components/schemas/DatasetConsumer' ErrorResponse: type: object required: - error properties: error: type: object required: - message - type - code properties: message: type: string type: type: string enum: - invalid_request_error - authentication_error - permission_error - not_found_error - rate_limit_error - server_error - service_unavailable - billing_error code: type: string enum: - INVALID_REQUEST - INVALID_API_KEY - OPERATION_NOT_ALLOWED - TENANT_SUSPENDED - AGREEMENT_REQUIRED - DATA_RESIDENCY_VIOLATION - PROVIDER_NOT_ALLOWED - PROVIDER_SERVICE_UNAVAILABLE - INSUFFICIENT_BALANCE - PAYMENT_REQUIRED - MODEL_NOT_FOUND - MODEL_ALREADY_EXISTS - DATASET_NOT_FOUND - DATASET_ALREADY_EXISTS - DATASET_STATE_INVALID - DATASET_IN_USE - DATASET_TOO_LARGE - JSONL_LINE_NOT_OBJECT - JSONL_MISSING_FIELD - JSONL_ENCODING - JOB_NOT_FOUND - JOB_STATE_INVALID - TRAINING_RUN_ABANDONED - TRAINING_TOKENIZE_FAILED - TRAINING_BASE_NOT_EXPORTABLE - IDEMPOTENCY_CONFLICT - QUOTA_EXCEEDED - INTERNAL - STORAGE_UNAVAILABLE param: type: - string - 'null' DatasetValidation: type: object properties: totalLines: type: string format: int64 validLines: type: string format: int64 firstErrorLine: type: string format: int64 errorClass: type: string enum: - JSONL_LINE_NOT_OBJECT - JSONL_MISSING_FIELD - JSONL_ENCODING DatasetConsumer: type: object properties: name: type: string kind: type: string enum: - DATASET_CONSUMER_KIND_TRAINING_JOB - DATASET_CONSUMER_KIND_BATCH_JOB - DATASET_CONSUMER_KIND_EVALUATION_JOB - DATASET_CONSUMER_KIND_DATASET pinnedVersion: type: string state: type: string blocksDelete: type: boolean headers: x-request-id: schema: type: string required: true description: >- On every response, successes and errors alike. Quote it when you ask us about a call. Retry-After: schema: type: integer minimum: 0 description: How many seconds to wait before retrying, on the responses that set it. responses: Error400: headers: x-request-id: $ref: '#/components/headers/x-request-id' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- `error.code` is one of: `DATASET_STATE_INVALID`, `INVALID_REQUEST`, `JSONL_ENCODING`, `JSONL_LINE_NOT_OBJECT`, `JSONL_MISSING_FIELD`, `TRAINING_BASE_NOT_EXPORTABLE`, `TRAINING_TOKENIZE_FAILED`. See the Errors page for what each one means, whether it is safe to retry, and whether it is billed. Error401: headers: x-request-id: $ref: '#/components/headers/x-request-id' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- `error.code` is one of: `INVALID_API_KEY`. See the Errors page for what each one means, whether it is safe to retry, and whether it is billed. Error403: headers: x-request-id: $ref: '#/components/headers/x-request-id' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- `error.code` is one of: `AGREEMENT_REQUIRED`, `DATA_RESIDENCY_VIOLATION`, `OPERATION_NOT_ALLOWED`, `PROVIDER_NOT_ALLOWED`, `PROVIDER_SERVICE_UNAVAILABLE`, `TENANT_SUSPENDED`. See the Errors page for what each one means, whether it is safe to retry, and whether it is billed. Error404: headers: x-request-id: $ref: '#/components/headers/x-request-id' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- `error.code` is one of: `DATASET_NOT_FOUND`, `JOB_NOT_FOUND`, `MODEL_NOT_FOUND`. See the Errors page for what each one means, whether it is safe to retry, and whether it is billed. Error500: headers: x-request-id: $ref: '#/components/headers/x-request-id' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- `error.code` is one of: `INTERNAL`, `TRAINING_RUN_ABANDONED`. See the Errors page for what each one means, whether it is safe to retry, and whether it is billed. Error503: headers: x-request-id: $ref: '#/components/headers/x-request-id' Retry-After: $ref: '#/components/headers/Retry-After' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- `error.code` is one of: `STORAGE_UNAVAILABLE`. See the Errors page for what each one means, whether it is safe to retry, and whether it is billed. securitySchemes: bearerAuth: type: http scheme: bearer description: >- `Authorization: Bearer ` -- the same key as inference. A key reaches the account it belongs to and no other. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.