Skip to content
Hayonix

API reference · Pods

The pod’s timeline (oldest first): what the platform did and what its host reported

GET/v1/pods/{pod_id}/events
API keyworkload:readProjectPaginated
TypeScript
client.pods.listEvents()
Python
client.pods.list_events()
CLI
hayonix pods events

Events such as placement, waiting for capacity, preemption, start and stop requests, reconfiguration and failures, oldest first. Events are kept after the container is gone.

Project API key (Authorization: Bearer sk_…), or a console session. Requires the workload:read permission (a key's scope, or a role that includes it).

Examples

The samples read API_KEY and API_BASE_URL from the environment (see Setup). Values are examples.

curl -sS "$API_BASE_URL/pods/pod_01jc5zq4m8k3v6x9t2w7r0b1e4/events" \
  -H "Authorization: Bearer $API_KEY"

Request

Headers
HeaderRequiredDescription
AuthorizationyesBearer and your API key. The key implies its project.
X-Project-Idsession onlyThe project to act in, for console sessions. Requests with an API key leave it out.

Path parameters

  • pod_idstringrequired

    ID of the pod

    ID with prefix pod_

Query parameters

  • limitinteger

    Events per page, 1–200 (default 100)

    1–200

  • cursorstring

    `next_cursor` of the previous page (events are oldest first)

    up to 200 characters

Response

200 a page of results — A page of events

  • dataarray of PodEventrequired

    The items of this page.

    Show 7 fields of data
    • objectstringrequired

      Always `pod_event`: the type of this object

      One ofpod_event

    • idstringrequired

      Unique ID

    • typestringrequired

      What happened, for example `placed`, `waiting`, `preempted`, `start_requested`, `stop_requested`, `reconfigured` or `terminated`

    • severitystringrequired

      `info`: routine. `warning`: may need attention. `error`: something failed.

      One ofinfowarningerror

    • messagestringrequired

      One sentence for people

    • dataobject | nullrequired

      Details; their shape depends on the kind of entry

    • occurred_atstring (date-time)required

      When it happened (ISO 8601, UTC)

  • next_cursorstring | nullrequired

    Pass as `cursor` for the next page; null on the last page.

Example response
Example response
{
  "data": [
    {
      "object": "pod_event",
      "id": "string",
      "type": "placed",
      "severity": "info",
      "message": "string",
      "data": {},
      "occurred_at": "2026-01-01T00:00:00.000Z"
    }
  ],
  "next_cursor": "string"
}

Errors

Errors use the standard envelope. What this operation can answer:

Errors
StatusTypeWhen
400invalid_request_errorA parameter or body field is missing or not allowed; param names it.
401authentication_errorThe key or session is missing, revoked or expired.
403permission_errorThe credential lacks the permission this needs, or the organization is suspended.
404not_found_errorNo such resource in this project (an ID from another project is answered the same way).
429rate_limit_error rate_limitedToo many requests; retry after retry-after seconds.