Run a SerpApi search | NativePort

Relays to https://serpapi.com/search, slotting the secret api_key in at the front of the query string. GET only. Controls ride the query string and reach SerpApi verbatim — the gateway defaults nothing (SerpApi’s own default for engine is google). Any client api_key in the query is dropped.

Authentication

AuthorizationBearer

Your per-client bearer token — the API key the gateway issued to you. Present it in Authorization: Bearer <token> form. A token that is missing, unknown, or revoked draws a 401. Before the call is sent upstream the token is removed (stripped, or swapped for the upstream’s own credential); it never makes it past the gateway.

Query parameters

enginestringOptional

Which engine to search. Left unset, SerpApi falls back to google.

qstringOptional

The query text.

locationstringOptional

Where the search should geographically originate.

outputenumOptional

Format of the reply — default json; choose html to get the raw SERP page.

Allowed values:

Response

Whatever the upstream answered, relayed as-is (status, headers, body). Rendered here as JSON; the true shape is the upstream provider’s to define.

Errors

401

Unauthorized Error

404

Not Found Error

$	curl -G https://api.nativeport.ai/serpapi \
>	-H "Authorization: Bearer <token>" \
>	-d engine=google \
>	--data-urlencode "location=Austin, Texas, United States" \
>	-d output=json \
>	-d q=coffee

1	{
2	"organic": [
3	{
4	"link": "https://www.apple.com/",
5	"position": 1,
6	"title": "Apple"
7	}
8	],
9	"searchParameters": {
10	"q": "apple inc",
11	"type": "search"
12	}
13	}