SHOW API ENDPOINT RUNS

Lists invocation history for a single API endpoint, one row per INVOKE, with run status, page/byte counts, watermark progression, and error summary when applicable.

Category: api-endpointPrivilege: adminDeltaForge extension

Syntax

SHOW API ENDPOINT RUNS <name> [LIMIT <n>]

Description

## Overview SHOW API ENDPOINT RUNS is the audit surface for a single endpoint's production history. It reads the run log populated by INVOKE API ENDPOINT and returns rows ordered newest-first. Typical columns: run_id, started_at, finished_at, status (success / failed / running), pages_fetched, rows_landed, bytes_written, watermark_before, watermark_after, landed_folder, error_message. ## Behavior - Only INVOKE invocations appear. CALL API ENDPOINT is preview-only and does not write to the run log. - A run still in the 'running' state, typical during a long-running ALLOW CONCURRENT fan-out, is included. - Error runs carry the server-side error message plus the HTTP status code that caused the failure. ## Access Control Requires the admin role. ## Compatibility DeltaForge extension.

Parameters

Name	Type	Description
`name`		Target endpoint as <zone>.<api>.<name>.
`limit`		Maximum number of most-recent runs to return. Omit for an engine-default cap.

Examples

SHOW API ENDPOINT RUNS landing.github.issues;

SHOW API ENDPOINT RUNS landing.github.issues LIMIT 20;

Pitfalls

CALL API ENDPOINT does NOT write to the run log by design (it is for authoring, not auditing). If you are debugging a 'nothing is happening' workflow, confirm you are running INVOKE, not CALL.
When ALLOW CONCURRENT is used, multiple overlapping rows can appear with status = running for the same endpoint. The engine does not merge or reconcile those, each invocation owns its own run log row.