POST /api/startpage/search
Price: 20 credits
Search Startpage by query and return organic web results. Each result has the target url, title, result description (snippet) and displayed url breadcrumb. Supports language, region, safe search and recency filters.
Startpage web search by query. First result is most relevant. Privacy-focused engine that returns Google-quality organic results without tracking. Each result has url, title, description and displayed_url. Use count to control how many results to return; language, region, safe_search and time_range to refine the search.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)query string required — Search query (examples: "python fastapi"; minLength: 1)count integer required — Maximum number of results (min: 1)language string nullable — Language of the search results (one of: "afrikaans", "arabic", "amharic", "azerbaijani", "indonesian", "malay", "bulgarian", "bengali", "javanese", "sudanese", "bosnian", "brazilian", "belarusian", "catalan", "czech", "welsh", "dansk", "deutsch", "estonian", "greek", "english", "espanol", "esperanto", "basque", "persian", "tagalog", "faroese", "francais", "frisian", "irish", "gaelic", "galician", "gujarati", "hindi", "croatian", "interlingua", "xhosa", "zulu", "icelandic", "italiano", "hebrew", "kannada", "georgian", "swahili", "latin", "latvian", "lithuanian", "hungarian", "bihari", "macedonian", "malayalam", "maltese", "marathi", "nederlands", "nepali", "norsk", "uzbek", "occitan", "thai", "polski", "portugues", "punjabi", "romanian", "russian", "albanian", "sinhalese", "slovak", "slovenian", "serbian", "suomi", "svenska", "tamil", "telugu", "vietnamese", "tigrinya", "turkce", "ukrainian", "urdu", "hangul", "jiantizhongwen", "nihongo", "fantizhengwen")region string — Region the results are tailored to (default: "all"; one of: "all", "argentina", "australia", "austria", "belarus", "belgium_fr", "belgium_nl", "brazil", "bulgaria", "canada_en", "canada_fr", "chile", "china", "colombia", "czech_republic", "denmark", "egypt", "estonia", "finland", "france", "germany", "greece", "hong_kong", "hungary", "india_en", "india_hi", "indonesia_en", "indonesia_id", "ireland", "italy", "japan", "korea", "malaysia_en", "malaysia_ms", "mexico", "netherlands", "new_zealand", "norway", "peru", "philippines_en", "philippines_fil", "poland", "portugal", "romania", "russia", "singapore_en", "singapore_ms", "south_africa", "spain_ca", "spain_es", "sweden", "switzerland_de", "switzerland_fr", "switzerland_it", "taiwan", "turkey", "ukraine", "united_kingdom", "uruguay", "us_en", "us_es", "venezuela", "vietnam_en", "vietnam_vi")safe_search string — Adult content filtering level (default: "moderate"; one of: "strict", "moderate", "off")time_range string — Restrict results to a recency window (default: "any"; one of: "any", "day", "week", "month", "year")@type string (default: "StartpageSearchResult")url string requiredsource string nullabledescription string (default: "")displayed_url string nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.