API reference · Dedicated endpoints
What happened to an endpoint, newest first
/v1/endpoints/{dedicated_endpoint_id}/events- 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
| Header | Required | Description |
|---|---|---|
Authorization | yes | Bearer and your API key. The key implies its project. |
X-Project-Id | session only | The project to act in, for console sessions. Requests with an API key leave it out. |
Path parameters
dedicated_endpoint_idstringrequiredID of the dedicated endpoint
ID with prefix ded_
Query parameters
limitinteger1–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.
ShowHide 10 fields of
dataobjectstringrequiredAlways `endpoint_event`: the type of this object
One of
endpoint_eventidstringrequiredUnique ID (`eev_…`)
ID with prefix eev_
endpoint_idstringrequiredID of the endpoint
deployment_idstring | nullrequiredID of the deployment
replica_idstring | nullrequiredID of the replica
typestringrequiredcreated, 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 of
infowarningerrormessagestringrequiredOne sentence for people
dataobjectrequiredDetails; their shape depends on the kind of entry
occurred_atstring (date-time)requiredWhen it happened (ISO 8601, UTC)
next_cursorstring | nullrequiredPass as `cursor` for the next page; null on the last page.
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:
| Status | Type | When |
|---|---|---|
400 | invalid_request_error | A parameter or body field is missing or not allowed; param names it. |
401 | authentication_error | The key or session is missing, revoked or expired. |
403 | permission_error | The credential lacks the permission this needs, or the organization is suspended. |
404 | not_found_error | No such resource in this project (an ID from another project is answered the same way). |
429 | rate_limit_error rate_limited | Too many requests; retry after retry-after seconds. |