The first step of deploying a folder: say what the archive is (a
gzipped tar of the folder) and get where its parts go. Send each part
with uploadSourcePart, then completeSourceUpload, then deploy (or
createService) with the uploadId. At most
PYO_SOURCE_UPLOAD_MAX_BYTES (500 MB by default). Kept for 2 hours.
API key access: deploy.
apiKeyAuthorizationBearer <pyo_…>An API key from the dashboard's API keys page: Authorization: Bearer pyo_…. Keys can expire, and an expired one gets a 401.
application/jsonA folder about to be uploaded.
teamId*stringThe team's id.
size*integerThe archive's size in bytes (a gzipped tar).
int640 <= valuesha256*stringIts SHA-256, in lowercase hex.
files?integerHow many files it holds.
int320 <= valuefolder?stringThe folder's name, shown with the deployment.
machine?stringThe computer's name, shown as "Uploaded from …".
uploadId, partSize (bytes in each part but the last), parts (how many) and expiresAt.
application/jsoncurl -X POST 'https://your-pyo.example.com/api/v1/source-uploads' \
-H 'Content-Type: application/json' \
-d '{
"teamId": "string",
"size": 0,
"sha256": "string"
}'{}