Xeonr Developer Docs

StartBlobUpload

POST
/uplim.api.v1.InternalPipelineRunsService/StartBlobUpload

-------- Streamed (multipart) blob output (M0.5) -------- For PutBlobOutput / CommitBlobOutputFile on the side-car socket: the side-car streams bytes to S3 without any presigned URL or bucket credential crossing the socket to user code. The api holds the creds and initiates the S3 multipart upload; only the side-car sees the per-part presigned PUT URLs. StartBlobUpload → PresignUploadPart (per ~5MB part) → CompleteBlobUpload; the side-car then calls the existing FinaliseBlobOutput (same object key) for the metadata write.

AuthorizationBearer <token>

JWT access token obtained via OAuth2 flow or service account

In: header

Header Parameters

Connect-Protocol-Version*number

Define the version of the Connect protocol

Value in1
Connect-Timeout-Ms?number

Define the timeout, in ms

Request Body

application/json

runId?string
Formatuuid
stepId?string
outputName?string
mime?string
filename?string

Optional per-file key for multi-file outputs; matches the filename threaded into MintBlobOutputUpload / FinaliseBlobOutput.

[key: string]?never

Response Body

application/json

application/json

curl -X POST "https://uploads-api.xeonr.io/uplim.api.v1.InternalPipelineRunsService/StartBlobUpload" \  -H "Connect-Protocol-Version: 1" \  -H "Content-Type: application/json" \  -d '{}'
{
  "objectKey": "string",
  "uploadId": "string"
}
{
  "code": "not_found",
  "message": "string",
  "details": [
    {
      "type": "string",
      "value": "string",
      "debug": {}
    }
  ]
}