List Adhoc Executions
List execution history for ad-hoc retrievers.
Returns execution history for all ad-hoc retriever executions in the namespace, sorted by timestamp descending (most recent first).
Use Cases:
- Track ad-hoc retriever usage across the namespace
- Debug ad-hoc retriever executions
- Analyze query patterns from ad-hoc searches
- Monitor performance of ad-hoc executions
Filtering:
- Filter by status (completed, failed, etc.)
- Filter by time range (start_time, end_time)
Pagination:
- Supports offset-based pagination via query parameters
- Default limit: 20, max limit: 100
- Use ?page_size=X&page_number=Y for pagination
Authorizations
Mixpeek API key, sent as Authorization: Bearer mxp_sk_.... Create one in Studio under Settings → API Keys, or with an admin key via POST /v1/organizations/users/{user_email}/api-keys. A missing header returns 403; an invalid or revoked key returns 401.
Namespace id (ns_...), not the namespace name. This scopes the request rather than authenticating it, and it is required on every operation marked x-mixpeek-namespace-scoped.
Query Parameters
1 <= x <= 10001 <= x <= 10000 <= x <= 10000x >= 1Body
Request to list ad-hoc retriever executions with filtering.
Allows filtering by status, time range, and searching by query summary. Results are ordered by timestamp descending (most recent first).
Filter by execution status. Common values: 'completed', 'failed'. OPTIONAL - omit to see all statuses.
"completed"
Filter executions after this timestamp (inclusive). OPTIONAL - omit for no start time filter.
Filter executions before this timestamp (inclusive). OPTIONAL - omit for no end time filter.
BACKE-3071: when true, return ONLY the total count and skip fetching the execution rows. Use for a badge/total (the Executions-tab count) — it avoids the ORDER BY full-row scan that made a limit:1 count take 15s+.

