Query History API

Azure Blob Storage joins the sync providers: POST /v2/collections/{collection_name}/sync/azure keeps an Azure container synced with a collection. Authenticate with the storage account’s name and access key (container + account_name + account_key; the key is stored securely, never returned, and rotates in place via PATCH /v2/syncs/{sync_id} with an account_key field). Reconciliation defaults to a 60-minute cadence, and real-time events arrive through an Event Grid subscription: one click with the Deploy to Azure template, or one az eventgrid event-subscription create: the setup guide shows both. The template is self-verifying: the deployment only goes green when Event Grid proves delivery to Captain and Captain confirms the webhook enrollment.

Your query history, from the API: GET /v2/queries lists the queries your keys and agents have run, newest first, scoped to the calling key’s environment, with collection, status, from/to and sort filters and cursor paging. GET /v2/queries/{query_id} returns one query with its request body, response body and the retrieved chunks in one normalised shape across v2 and v3. Add include=results,request,response to the list to get feed and previews in one request; the body fields are always present and null unless requested. Bodies are archived 90 days after the query (body_status: archived); summaries are kept.
Query responses now carry query_id: every POST .../query response (v2 and v3) returns the id of its history row, so you can fetch it back with GET /v2/queries/{query_id} straight away. The request_id a query response returns is accepted on that endpoint too.