Skip to main content
GET
/
enterprise
/
v1
/
io-cloud
/
caas
/
deployment
/
{deployment_id}
/
log
/
{container_id}
Get Container Log Stream
curl --request GET \
  --url https://api.io.solutions/enterprise/v1/io-cloud/caas/deployment/{deployment_id}/log/{container_id} \
  --header 'Authorization: Bearer <token>'
"<any>"

Fetching Container Logs via API

  • The logs endpoint always produces a chunked response - it’s a stream.
  • Specifically, it uses Server-Sent Events (SSE) for streaming logs.
  • Do not use response.json(); consume the logs line-by-line.
  • Currently, the API spec is incomplete:
    • offset and stream type query parameters are missing.
    • Public API specs need a full review to match Swagger; other fields may be missing.

Python Example

import requests

# Replace with your Deployment and Log IDs
deployment_id = "Deployment ID"
log_id = "Log ID"

url = "https://api.io.solutions/enterprise/v1/io-cloud/caas/deployment/{deployment_id}/log/{log_id}"
headers = {
    "X-API-KEY": "YOUR_API_KEY",
    "Content-Type": "application/json"
}

# Use stream=True to handle the response incrementally
with requests.get(url, headers=headers, stream=True) as r:
    r.raise_for_status()
    for line in r.iter_lines():
        if line:
            print(line.decode("utf-8"))

Notes

  • Treat all responses as streams, not JSON.
  • Each line corresponds to a log entry (stdout/stderr), as seen in the UI.
  • SSE allows for real-time log consumption for monitoring/debugging.

Authorizations

Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Headers

x-api-key
string

io.net provided API Key

Path Parameters

deployment_id
string<uuid>
required
container_id
string
required

Query Parameters

stream
enum<string>
default:stdout
Available options:
stdout,
stderr

Response

Successful Response

The response is of type any.

I