Geotargeting

Local content

Every HTTP request can be routed through one of more than 190 countries, by subdivision and city:

curl -H "Authorization: Bearer $MASSIVE_TOKEN" \
'https://render.joinmassive.com/search'\
'?terms=musical+instruments'\
'&country=US'

View subdivision example

curl -H "Authorization: Bearer $MASSIVE_TOKEN" \
'https://render.joinmassive.com/ai'\
'?prompt=Where+can+I+buy+a+vintage+guitar%3F'\
'&country=US'\
'&subdivision=TN'

View city example

curl -H "Authorization: Bearer $MASSIVE_TOKEN" \
'https://render.joinmassive.com/browser'\
'?url=https://guitars.com/'\
'&country=US'\
'&city=Nashville'

These are the geotargeting request parameters:

Key	Required	Value
`country`	⬜	The two-letter ISO code of the country to browse from (these codes are case insensitive); a random country is used by default
`subdivision`	⬜	The alphanumeric second part (proceeding the separator) of a first-level subdivision code in the (prerequisite) country to browse from (these codes are case insensitive); a random subdivision is used by default
`city`	⬜	The commonly spelled name of the city in the (prerequisite) country to browse from (these names are temporarily case sensitive and required to include form- or URL-encoded spaces and punctuation marks); a random city is used by default

City targeting takes precedence over subdivision targeting if both are specified.

These are the response parameters:

Key	Value
`country`	The ISO code of the country that was browsed from
`subdivision`	The partial ISO code of the subdivision in the country that was browsed from
`city`	The common name of the city in the country that was browsed from

SchedulingDefer responses for later retrieval.

Get started

Endpoints

Configuration

API Management

API Reference

Local content

​Local content

Local content