Skip to content
Hayonix

API reference · Dedicated endpoints

What happened to an endpoint, newest first

GET/v1/endpoints/{dedicated_endpoint_id}/events
API keydedicated_endpoint:readProjectPaginated
TypeScript
client.dedicatedEndpoints.listEvents()
Python
client.dedicated_endpoints.list_events()
CLI
hayonix endpoints events

A history of changes to the endpoint, its deployments and replicas: starts and stops (including automatic ones), traffic changes, replicas starting, becoming ready, failing or being removed.

Project API key (Authorization: Bearer sk_…), or a console session. Requires the dedicated_endpoint: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/endpoints/ded_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

  • dedicated_endpoint_idstringrequired

    ID of the dedicated endpoint

    ID with prefix ded_

Query parameters

  • limitinteger

    1–200, default 50

    1–200

  • cursorstring

    `next_cursor` of the previous page

    up to 200 characters

Response

200 a page of results — A page of events

  • The items of this page.

    Show 10 fields of data
    • objectstringrequired

      Always `endpoint_event`: the type of this object

      One ofendpoint_event

    • idstringrequired

      Unique ID (`eev_…`)

      ID with prefix eev_

    • endpoint_idstringrequired

      ID of the endpoint

    • deployment_idstring | nullrequired

      ID of the deployment

    • replica_idstring | nullrequired

      ID of the replica

    • typestringrequired

      created, started, stopped, deleted, deployment_created, deployment_updated, deployment_deleted, traffic_split, replicas_started, replica_ready, replica_unhealthy, replicas_draining, replica_removed, replica_failed, deployment_failed

    • severitystringrequired

      `info`: a routine change. `warning`: needs attention (an automatic stop, an unhealthy replica, a replica or deployment that failed to start). `error`: a serious failure

      One ofinfowarningerror

    • messagestringrequired

      One sentence for people

    • dataobjectrequired

      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": "endpoint_event",
      "id": "eev_01jc5zq4m8k3v6x9t2w7r0b1e4",
      "endpoint_id": "string",
      "deployment_id": "string",
      "replica_id": "string",
      "type": "replica_ready",
      "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.