Authorizations
Bearer token authentication using your API key. Format: 'Bearer your_api_key'. To get an API key, create an account at mixpeek.com/start and generate a key in your account settings.
Headers
REQUIRED: Bearer token authentication using your API key. Format: 'Bearer sk_xxxxxxxxxxxxx'. You can create API keys in the Mixpeek dashboard under Organization Settings.
"Bearer sk_live_abc123def456"
"Bearer sk_test_xyz789"
REQUIRED: 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'
"ns_abc123def456"
"production"
"my-namespace"
Body
Request for listing interactions with filters.
Supports both simple field filters (for common queries) and advanced LogicalOperator filters (for complex analytics). This hybrid approach follows the same pattern as the Tasks module.
Common Queries (Simple Fields): - Filter by execution: {"execution_id": "exec_abc"} - Filter by session: {"session_id": "sess_xyz"} - Filter by user: {"user_id": "user_123"}
Advanced Queries (LogicalOperator): - Range queries: {"filters": {"position": {"lte": 5}}} - Complex logic: {"filters": {"AND": [...]}} - Time ranges: {"filters": {"created_at": {"gte": "2025-01-01"}}}
Filter by retriever execution ID. Most common query: find all interactions from a specific search execution. Example: 'exec_abc123'
"exec_abc123"
"exec_550e8400e29b"
Filter by retriever ID. Compare performance across different retriever configurations. Example: 'ret_product_search_v2'
"ret_product_search"
"ret_baseline_v1"
Filter by session ID. Track user journey across multiple searches within a session. Example: 'sess_xyz789'
"sess_abc123"
"sess_xyz789_1234567890"
Filter by user ID. Analyze behavior of specific users for personalization insights. Example: 'user_456'
"user_abc123"
"customer_456"
Filter by feature/document ID. Find all interactions with a specific document across all searches. Example: 'doc_abc123'
"doc_abc123"
"prod_xyz789"
Filter by interaction type. Use to find specific behaviors like clicks, purchases, or feedback. Example: 'click', 'positive_feedback'
"click"
"positive_feedback"
"purchase"
Advanced filters using LogicalOperator for complex analytics queries. Supports shorthand syntax and complex AND/OR/NOT logic. Use this for: range queries, complex conditions, metadata filtering. Examples: - Position range: {'position': {'lte': 5}} - Time range: {'timestamp': {'gte': '2025-01-01'}} - Complex: {'AND': [{'field': 'position', 'operator': 'lte', 'value': 5}, {'field': 'interaction_type', 'operator': 'in', 'value': ['click', 'purchase']}]} See LogicalOperator documentation for full syntax. Represents a logical operation (AND, OR, NOT) on filter conditions.
Allows nesting with a defined depth limit.
Also supports shorthand syntax where field names can be passed directly as key-value pairs for equality filtering (e.g., {"metadata.title": "value"}).
{ "position": { "lte": 5 } }{
"AND": [
{
"field": "position",
"operator": "lte",
"value": 5
},
{
"field": "interaction_type",
"operator": "in",
"value": ["click", "purchase"]
}
]
}{
"OR": [
{
"field": "interaction_type",
"operator": "eq",
"value": "purchase"
},
{
"field": "metadata.duration_ms",
"operator": "gte",
"value": 10000
}
]
}Sort options for ordering results. Default: timestamp descending (newest first). Examples: - Sort by timestamp: {'field': 'timestamp', 'direction': 'desc'} - Sort by position: {'field': 'position', 'direction': 'asc'} Specifies how to sort query results.
Attributes: field: Field to sort by direction: Sort direction (ascending or descending)
{ "direction": "desc", "field": "timestamp" }{ "direction": "asc", "field": "position" }Full-text search across metadata fields. NOT REQUIRED. Use to search interaction metadata content.
"mobile device"
"campaign_summer_2024"
Response
Successful Response

