Saved searches run
POST /v1/saved-searches/{search_id}/runRun a saved search now and return its rows.
Authenticate with an API key from the API & MCP Hub. The same call is available as an MCP tool at the same price.
Reference
What POST /v1/saved-searches/{search_id}/run returns
Charged at the UNDERLYING tool's price, against that tool's own pricing key — a saved sourcing search bills exactly as a direct one does. There is no discount for saving and no surcharge.
Nothing runs in the background: a saved search costs nothing while it merely exists, and this is the only call that spends. Where the tool carries a change-feed cursor, the stored one is passed in and the new one is written back, so consecutive runs answer "what changed" rather than repeating the whole result.
Request
Calling POST /v1/saved-searches/{search_id}/run
curl -X POST "https://api.marketcode.ai/v1/saved-searches/%3Csearch_id%3E/run" \
-H "Authorization: Bearer $MARKETCODE_API_KEY"
-H "Content-Type: application/json" \
-d '{}'Send your API key as a Bearer token. Every response carries credits_charged and credits_remaining.
Inputs
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| search_id | Path | string | Yes |
Price and licence
What it costs, and where the data comes from
The price of Saved searches run is not in the live price table yet; the page shows a dash rather than a guess.
Credits are granted on sign-up and bought in packs; the pricing page lists every call.
FAQ
Questions about Saved searches run
How much does `saved-searches-run` cost?
+
The price of Saved searches run is not in the live price table yet; the page shows a dash rather than a guess.
How do I authenticate?
+
Send your API key as a Bearer token in the Authorization header. Keys are created in the API & MCP Hub, shown once and revocable. Every response carries the credits charged and your remaining balance.
Try Saved searches run on a real address.
30-minute call. We'll provision a key and walk through the endpoint on your use case.