Skip to content
Helicarrier Developers

Get logs

Read runtime output from a service. Filter historical logs or read incrementally with a cursor.

GET /api/services/{id}/logs HTTPS
Request & response examples
Request example Server-side
curl --fail-with-body --request GET \
'https://app.helicarrier.xyz/api/services/YOUR_ID/logs?limit=25' \
-H "Authorization: Bearer $HELI_API_KEY"
Response example 200
{
"logs": [
{
"id": 42,
"serviceId": "svc_example",
"line": "Listening on port 3000",
"stream": "app",
"ts": "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

id string required

Service id.

Query parameters

limit integer optional

Max lines.

q string optional

Substring filter.

before integer optional REST only

Return lines older than this log ID.

after integer optional REST only

Return newer lines for live tailing. In this mode, search and time filters are not applied.

since string optional REST only

Inclusive RFC3339 timestamp filter.

until string optional REST only

Exclusive RFC3339 timestamp filter.

Response 200

Returns { "logs": [...] }. Each entry is a runtime log record. Use after for an incremental REST tail or combine before, q, since, and until to inspect historical output.

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

logs array

Runtime log records.

Child fields
  • id integer

    Unique identifier of this resource.

  • serviceId string
  • line string

    One line of log output.

  • stream string

    Log stream that produced this line.

  • ts string

    Runtime log timestamp.

Errors

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

get_logs

Required MCP arguments: id. Send path, query, and body fields together as tool arguments. Parameters marked REST only are not available through this tool.

Connect your agent ↗