Adhoc Retrievers

List Adhoc Executions

Changed on

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

post/v1/retrievers/executions/list

Request

  • Base URL: https://api.mixpeek.com
  • URL: https://api.mixpeek.com/v1/retrievers/executions/list
  • Auth: HTTP bearer and API key in header X-Namespace

Query parameters

limitinteger nullable
page_sizeinteger nullable
offsetinteger nullable
pageinteger nullable
cursorstring nullable
next_cursorstring nullable
afterstring nullable
include_totalboolean

Request body

statusstring nullable

Filter by execution status. Common values: 'completed', 'failed'. OPTIONAL - omit to see all statuses.

start_timeunknown
end_timeunknown
count_onlyboolean

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+.

Example request

{
  "status": "completed"
}

Response

Successful Response

totalinteger

Total number of ad-hoc executions matching filters.

paginationunknown required

Changes

    • warning

      removed the optional property from the response with the status

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      added the optional property to the response with the status

    • info

      added the required property to the response with the status

    • info

      added the required property to the response with the status

    • info

      the endpoint scheme security BearerAuth AND NamespaceHeader was added to the API