Create Batch

The time frame within which the batch should be processed. Currently only 24h is supported.

The endpoint to be used for all requests in the batch. Currently /v1/chat/completions, /v1/embeddings, and /v1/completions are supported. Note that /v1/embeddings batches are also restricted to a maximum of 50,000 embedding inputs across all requests in the batch.

The ID of an uploaded file that contains requests for the new batch.

See upload file for how to upload a file.

Your input file must be formatted as a JSONL file, and must be uploaded with the purpose batch. The file can contain up to 50,000 requests, and can be up to 100 MB in size.

Optional custom metadata for the batch.

The time frame within which the batch should be processed.

The Unix timestamp (in seconds) for when the batch was created.

The Portkey API endpoint used by the batch.

The ID of the input file for the batch.

The object type, which is always batch.

The current status of the batch.

The Unix timestamp (in seconds) for when the batch was cancelled.

The Unix timestamp (in seconds) for when the batch started cancelling.

The Unix timestamp (in seconds) for when the batch was completed.

The ID of the file containing the outputs of requests with errors.

The Unix timestamp (in seconds) for when the batch expired.

The Unix timestamp (in seconds) for when the batch will expire.

The Unix timestamp (in seconds) for when the batch failed.

The Unix timestamp (in seconds) for when the batch started finalizing.

The Unix timestamp (in seconds) for when the batch started processing.

Set of 16 key-value pairs that can be attached to an object. This can be useful for storing additional information about the object in a structured format. Keys can be a maximum of 64 characters long and values can be a maxium of 512 characters long.

The ID of the file containing the outputs of successfully executed requests.

The request counts for different statuses within the batch.