Skip to content
Helicarrier Developers

Get deployment logs

Read build and deployment output, optionally after a previously seen log identifier.

GET /api/deployments/{deploymentId}/logs HTTPS
Request & response examples
Request example Server-side
curl --fail-with-body --request GET \
'https://app.helicarrier.xyz/api/deployments/YOUR_DEPLOYMENT_ID/logs?after=0' \
-H "Authorization: Bearer $HELI_API_KEY"
Response example 200
[
{
"id": 42,
"deploymentId": "dep_example",
"line": "Build completed",
"stream": "system",
"createdAt": "2026-10-07T12:00:00Z"
}
]

Illustrative values · selected fields

Authorization

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

Authorization: Bearer <key> Key setup ↗

Path parameters

deploymentId string required

Deployment id.

Query parameters

after integer optional

Return only lines after this sequence number, so a build can be followed incrementally instead of re-fetching the whole log each time.

Response 200

Returns a JSON array of deployment log records. Pass the last sequence number as after to read only newer lines.

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

id integer

Unique identifier of this resource.

deploymentId string

Identifier to use when reading deployment history or logs.

line string

One line of log output.

stream string

Log stream that produced this line.

createdAt string

Resource creation timestamp.

Errors

401

The API key is missing, invalid, or revoked.

403

The caller or key scope does not permit this operation.

404

The resource does not exist or is not visible to this caller.

500

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

Error handling and safe retries
ALSO AVAILABLE VIA MCP

get_deployment_logs

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

Connect your agent ↗