Skip to main content
GET
/
v1
/
analytics
/
retrievers
/
{retriever_id}
/
signals
Get Retriever Signals
curl --request GET \
  --url https://api.mixpeek.com/v1/analytics/retrievers/{retriever_id}/signals
[
  {
    "timestamp": "2023-11-07T05:31:56Z",
    "execution_id": "<string>",
    "signal_type": "<string>",
    "signal_data": {},
    "metadata": {}
  }
]

Documentation Index

Fetch the complete documentation index at: https://docs.mixpeek.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Headers

​
Authorization
string

REQUIRED: Bearer token authentication using your API key. Format: 'Bearer sk_xxxxxxxxxxxxx'. You can create API keys in the Mixpeek dashboard under Organization Settings.

Examples:

"Bearer YOUR_API_KEY"

"Bearer YOUR_STRIPE_API_KEY"

​
authorization
string
​
X-Namespace
string

Namespace identifier for scoping this request. All resources (collections, buckets, taxonomies, etc.) are scoped to a namespace. You can provide either the namespace name or namespace ID. Format: ns_xxxxxxxxxxxxx (ID) or a custom name like 'my-namespace'. Falls back to ?namespace= query parameter if the header is omitted.

Examples:

"ns_abc123def456"

"production"

"my-namespace"

Path Parameters

​
retriever_id
string
required

Query Parameters

​
signal_type
string | null

Filter by signal type (cache_hit, rerank_scores, etc.)

​
limit
integer
default:100

Maximum results

Required range: x <= 1000
​
hours
integer
default:24

Hours of history

Required range: 1 <= x <= 720

Response

Successful Response

​
timestamp
string<date-time>
required

Event timestamp

​
execution_id
string
required

Execution identifier

​
signal_type
string
required

Type of signal

Examples:

"cache_hit"

"rerank_scores"

"filter_reduction"

​
signal_data
Signal Data · object
required

Signal-specific data

​
metadata
Metadata · object

Additional metadata