Enriched Search
API-Enriched Search
Search results enriched with data from external APIs. Great for CRM integration, product data enrichment, etc.
No credit card to start · Build from $25/mo
Pipeline Stages
1
semantic_search
filter
feature_searchView parameters
{
"searches": [
{
"feature_uri": "mixpeek://text_extractor@v1/multilingual_e5_large_instruct_v1",
"query": {
"input_mode": "text",
"value": "{{INPUT.query}}"
},
"top_k": 50
}
],
"final_top_k": 20
}2
api_enrichment
apply
api_callView parameters
{
"url": "{{INPUT.api_url}}?id={{DOC.document_id}}",
"allowed_domains": [
"api.example.com"
],
"method": "GET",
"auth": {
"type": "bearer",
"secret_ref": "api_key"
},
"output_field": "metadata.api_data"
}3
format_output
apply
json_transformView parameters
{
"template": "{\"id\": \"{{DOC.document_id}}\", \"content\": \"{{DOC.content}}\", \"enriched_data\": {{DOC.metadata.api_data}}, \"score\": {{DOC.score}}}",
"fail_on_error": false
}Input Schema
querytext
required
Search query
api_urlstring
required
External API URL for enrichment, without a query string. Its domain must be in the stage's allowed_domains.
e.g. https://api.example.com/v1/records
Use Cases
- CRM data integration
- Product data enrichment
- Real-time pricing lookup
- External metadata fetching
Requirements
- External API must be accessible
- Set allowed_domains in the api_enrichment stage to your API's domain
- Store the API key in the organization secrets vault as 'api_key'
Tags
api
enrichment
integration
external
Ready to use this template?
Clone it into your namespace and start querying in minutes.