How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Zenserp Lists API

Reference list endpoints publishing the enumerations the Search API parameters must draw from: supported interface languages (hl), countries (gl), canonical Google geo-targeting locations, and search-engine domains.

Zenserp Lists API is one of 5 APIs that Zenserp publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include List, Reference Data, Geolocation, Language, and Countries. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, pricing, and authentication docs.

This API exposes 4 operations across 4 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://app.zenserp.com.

4 operations 4 paths 5 schemas 4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://app.zenserp.com/api/v2
Authentication
API Key, API Key
Terms of Service
Resource Areas
1

Authentication & Security 2

Zenserp Lists API declares 2 security schemes for authenticating requests. An API key is passed in the header as apikey (apiKeyHeader). An API key is passed in the query as apikey (apiKeyQuery). By default, every request must be authenticated.

  • apiKeyHeader — API key passed in the request header.
  • apiKeyQuery — API key passed as a query parameter.

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 4 GET. Each is listed below with its method, path, parameters, and response codes.

Lists 4

Reference list endpoints for supported languages, countries, locations, and engines.

GET
/api/v2/hl
Google Languages (hl)
listLanguages → 200403404500
GET
/api/v2/gl
Google Countries (gl)
listCountries → 200403404500
GET
/api/v2/locations
Geo Locations
listLocations → 200403404500
GET
/api/v2/search_engines
Google Search Engines
listEngines → 200403404500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are LocationItem (2 properties), CountryItem (2 properties), LanguageItem (2 properties), EngineItem (2 properties). Each schema is shown below with its type and property counts.

EngineItem
object
2 properties
ErrorResponse
object
Zenserp error envelope for request-level failures. Verbatim example from the live API: {"error": "No apikey provided."}
1 property
LanguageItem
object
2 properties
CountryItem
object
2 properties
LocationItem
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zenserp-lists-api-openapi.yml Raw ↑

Other APIs Zenserp publishes across the network.

Zenserp Batch API
Zenserp Search API
Zenserp Shopping Product Page API
Zenserp Trends API
Where this information came from

This is an independent, third-party profile of Zenserp Lists API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.