Serverless
Apps

Application Events

Returns the operational event history for an application: deployments, configuration changes, and runner lifecycle transitions (started, failed, draining, etc.), newest first.

Use cases:

  • Incident correlation: answer "what changed around this time?" — did a deploy, config change, or runner failure coincide with an error spike?
  • Deployment audit: see when revisions went out and who triggered them

Time range: defaults to the last 24 hours when start/end are omitted. Use category filters to narrow to specific event types.

Authentication: Required via API key. Only the app owner can query it.

get/serverless/apps/{owner}/{name}/events

Path parameters

ownerstring required

Username of the app owner

Example:user_123

Username of the app owner

namestring required

Application name

Example:my-app

Application name

Query parameters

string date-time
OR
string

Start date in ISO8601 format (e.g., '2025-01-01T00:00:00Z' or '2025-01-01'). Defaults to 24 hours ago.

string date-time
OR
string

End date in ISO8601 format, exclusive (e.g., '2025-02-01T00:00:00Z' or '2025-02-01'). Data up to but not including this timestamp is returned. Defaults to current time.

'runner_started' | 'runner_failed' | 'runner_finished' | 'runner_pending' | 'runner_startup_failure' | 'runner_docker_pull' | 'runner_setup' | 'runner_draining' | 'runner_stopping' | 'deployment_started' | 'deployment_failed' | 'deployment_ended' | 'deployment_rolling_started' | 'deployment_rolling_failed' | 'deployment_rolling_ended' | 'deployment_recreate_applied' | 'config_changed'
OR
string[]

Filter by event category. Repeat the parameter to include multiple categories: ?category=deployment_started&category=config_changed

limitinteger

Maximum number of events to return per page (1-1000)

Example:50

Maximum number of events to return per page (1-1000)

cursorstring

Pagination cursor from previous response

Example:Mg==

Pagination cursor from previous response

Response

Successfully retrieved application events

next_cursorstring nullable required

Cursor for the next page of results, null if no more pages

has_moreboolean required

Boolean indicating if more results are available (convenience field derived from next_cursor)

endpoint_idstring required

Canonical endpoint identifier ('<owner>/<name>')

Example response

{
  "endpoint_id": "user_123/my-app",
  "events": [
    {
      "event_id": "a1b2c3d4-0000-0000-0000-000000000000",
      "category": "deployment_started",
      "created_at": "2026-07-01T12:00:00Z",
      "payload": {
        "job_id": "5f8e9c2a",
        "machine_type": "GPU-H100",
        "state": "RUNNING",
        "actor": {
          "nickname": "user_123",
          "full_name": "Ada Lovelace"
        }
      }
    }
  ]
}

Changes

No recorded changes to this endpoint across all 2 revisions of this API.