Update uploaded source

Deploy a new source archive to an existing upload service while keeping its identity and configuration.

POST /api/services/{id}/upload-b64 HTTPS

Request & response examples

Request example Server-side

curl --fail-with-body --request POST \
  'https://app.helicarrier.xyz/api/services/YOUR_ID/upload-b64' \
  -H "Authorization: Bearer $HELI_API_KEY" \
  -H 'Content-Type: application/json' \
  --data '{
  "archiveBase64": "BASE64_ENCODED_SOURCE_ARCHIVE"
}'

const response = await fetch(
  "https://app.helicarrier.xyz/api/services/YOUR_ID/upload-b64",
  {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.HELI_API_KEY}`,
      "Content-Type": "application/json"
    },
    body: JSON.stringify({
      "archiveBase64": "BASE64_ENCODED_SOURCE_ARCHIVE"
    })
  }
);
const data = await response.json();
if (!response.ok) {
  throw new Error(`HTTP ${response.status}: ${data.error}`);
}
// Inspect data; avoid logging secret responses.

import os
import requests

response = requests.request(
    "POST",
    "https://app.helicarrier.xyz/api/services/YOUR_ID/upload-b64",
    headers={
        "Authorization": f"Bearer {os.environ['HELI_API_KEY']}"
    },
    json={
      "archiveBase64": "BASE64_ENCODED_SOURCE_ARCHIVE"
    },
    timeout=30,
)
response.raise_for_status()
data = response.json()
# Inspect data; avoid logging secret responses.

Response example 202

{
  "deploymentId": "dep_example"
}

Illustrative values · selected fields

Response details ↓ OpenAPI ↗

Authorization

An account key with access, or a project/service key with deployments:write. The resource must be within the key’s project, service, and environment scope.

Authorization: Bearer <key> Key setup ↗

Path parameters

id string required

Service id (an upload-source service).

Request body application/json

archiveBase64 string required

The new build context as a base64-encoded .tar.gz (or .zip) of your project folder. Exclude node_modules/.git to keep it small.

Response 202

Queues a new deployment for an existing upload service. Follow the returned deploymentId to inspect the result.

Examples show selected response fields with illustrative values. Your response can contain additional fields.

deploymentId string

Identifier to use when reading deployment history or logs.

Errors

400

Invalid parameters. Check the required fields, types, and resource configuration.

401

The API key is missing, invalid, or revoked.

403

The caller or key scope does not permit this operation.

500

The operation could not be completed. Check resource state before retrying a write.

Error handling and safe retries

ALSO AVAILABLE VIA MCP

`reupload_service`

Required MCP arguments: id, archiveBase64. Send path, query, and body fields together as tool arguments.

Connect your agent ↗

curl --fail-with-body --request POST \ 'https://app.helicarrier.xyz/api/services/YOUR_ID/upload-b64' \ -H "Authorization: Bearer $HELI_API_KEY" \ -H 'Content-Type: application/json' \ --data '{ "archiveBase64": "BASE64_ENCODED_SOURCE_ARCHIVE" }'

import os import requests response = requests.request( "POST", "https://app.helicarrier.xyz/api/services/YOUR_ID/upload-b64", headers={ "Authorization": f"Bearer {os.environ['HELI_API_KEY']}" }, json={ "archiveBase64": "BASE64_ENCODED_SOURCE_ARCHIVE" }, timeout=30, ) response.raise_for_status() data = response.json() # Inspect data; avoid logging secret responses.