Upload Model

Upload an ONNX model file (model.tar.gz) to a revision.

POST /revisions/:id/data/command (Command: upload)

Request Format

The model bytes travel in the request body, so the JSON command cannot. This endpoint reads a binary request: the file as the body, and the command as a header.

Header	Value
Content-Type	application/octet-stream
X-Request-Body	The JSON command below, serialized onto a single line.

X-Request-Body is named in the API’s Access-Control-Allow-Headers, so a browser client can send it.

Posting the command as a plain JSON body instead — Content-Type: application/json, no X-Request-Body — parses, but delivers no bytes, so it answers 400 upload_size_mismatch and stores nothing.

The archive travels inside the API request, which is limited to 6 MB once base64-encoded. Keep a single-part upload to 4 MiB or less, and send anything larger with Multipart Upload.

Request Body

Serialized into X-Request-Body, not into the body itself:

Parameter	Type	Required	Description
command	string	Yes	Must be upload.
path	string	Yes	File name, must be model.tar.gz.
size	integer	Yes	Size of the file in bytes. At least 1.

Response

Parameter	Type	Description
operation_id	string	ID of the background upload operation.

The file bytes travel in this request, so no upload URL comes back — the model is already stored by the time the command answers. Poll Get Operation with operation_id to follow the post-processing that unpacks it: the operation ends completed, or failed when the archive does not hold exactly one regular file named model.onnx that parses as an ONNX model.

Errors

Status	Error	Cause
400	invalid_request_body	path is not model.tar.gz, size is missing or below 1, or a field this page does not list was sent.
400	limit_exceeded	size is larger than onnx.model_bytes allows for this blob — 524,288,000 bytes by default. The check reads the declared size, before the body. See When a limit is reached.
400	upload_size_mismatch	The body’s length differs from size. A request with no body, such as a plain JSON one, holds 0 bytes.
403	forbidden	The revision does not exist, or the caller cannot write to its blob.
409	blob_not_ready	The blob is not ready: it is being created or deleted.
409	revision_not_ready	The revision’s status is not ready.
409	revision_not_writable	The revision is committed. Uploads go to a draft.

A refused upload stores nothing, creates no operation and starts no processing.

Example

Request

curl -X POST https://api.blobhub.io/v1/revisions/rev_001/data/command \
  -H "X-API-Key: $BLOB_API_KEY" \
  -H "Content-Type: application/octet-stream" \
  -H 'X-Request-Body: {"command":"upload","path":"model.tar.gz","size":154829}' \
  --data-binary @model.tar.gz