Xeonr Developer Docs

Start Blob Upload

POST
/uplim.api.v1.InternalPipelineRunsService/StartBlobUpload

Starts an S3 multipart upload for a streamed blob output at the same deterministic scratch key MintBlobOutputUpload would use, returning the object key and S3 upload id. The api holds the bucket credentials; the side-car then calls PresignUploadPart, CompleteBlobUpload and FinaliseBlobOutput. Same output-name namespace rules as MintBlobOutputUpload.

Access: internal only — step-scoped. Requires the per-step JWT in X-Upl-Step-Token (HS256 over PIPELINE_INTERNAL_TOKEN, unexpired) whose run_id/step_id claims match the request; Unauthenticated otherwise. The shared X-Upl-Internal-Token is accepted instead only while PIPELINE_ALLOW_LEGACY_STEP_TOKEN_FALLBACK is enabled.

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

Connect-Timeout-Ms?number

Define the timeout, in ms

Request Body

application/json

runId?string
Formatuuid
stepId?string
Lengthlength <= 255
outputName?string
Match^[a-z][a-z0-9-]{0,62}[a-z0-9]:[a-z][a-z0-9._-]{0,62}[a-z0-9]$
mime?string
Lengthlength <= 1024
filename?string

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

Lengthlength <= 1024
[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 "Connect-Timeout-Ms: 1000" \  -H "Content-Type: application/json" \  -d '{}'
{
  "objectKey": "string",
  "uploadId": "string"
}
{
  "code": "not_found",
  "message": "string",
  "details": [
    {
      "type": "string",
      "value": "string",
      "debug": {}
    }
  ]
}