Zenserp Migration Guide
Zenserp is a high-performance SERP (Search Engine Results Page) API designed to programmatically scrape and parse search results in real-time.
Why Developers Care
Infrastructure-as-a-Service
You donβt need to maintain a headless browser cluster, manage proxy pools, or solve CAPTCHAs.
Zenserp handles the entire request-to-result lifecycle.
Structured Data Extraction
Zenserp doesn’t just return HTML; it parses Organic results, Maps, YouTube, reverse image, and other search engine results into clean JSON objects.
Unlimited Concurrency
Other APIs (like SerpApi) throttle your parallel requests based on your plan. Zenserp allows you to send as many simultaneous requests as your application can handle, making it ideal for large-scale data ingestion.
This guide provides the technical essentials for migrating from SearchApi.io, SerpApi, and Serper.dev to Zenserp.
1. Authentication
All the SERP APIs typically use an API key query parameter to authenticate the requests. Zenserp uses the key apikey.
Zenserp looks for the API key in a header that looks like the following (recommended, works with all requests):
apikey: YOUR-APIKEY
For GET requests you can also use a URL parameter:
https://app.zenserp.com/api/v2/search?apikey=YOUR-APIKEY
For POST requests you can also use a form field:
apikey=YOUR-APIKEY
2. Base Endpoint & Basic Search
Zenserp uses a unified /search endpoint with query params for type, engine, etc. Following is the base URL:
https://app.zenserp.com/api/v2/search
Following are the Base endpoint changes from some of the famous SERP APIs:
| Source API | Example Base URL | Zenserp Equivalent |
|---|---|---|
| SearchAPI | https://www.searchapi.io/api/v1/search | https://zenserp.com/api/v2/search |
| SerpApi | https://serpapi.com/search?engine=google | https://zenserp.com/api/v2/search |
| Serper.dev | https://google.serper.dev/search | https://zenserp.com/api/v2/search |
Zenserp API follows the universal Query parameter q with Engine parameter engine (default: google). Check out the official documentation to learn all acceptable values of engine parameter.
Below table shows the common parameters mapping (cheat sheet):
| Search Feature | SearchApi / SerpApi | Serper.dev | Zenserp Equivalent |
|---|---|---|---|
| Search Engine | engine | (Path based) | engine (google, bing, yandex) |
| Location | location | gl / location | location |
| Language | hl | hl | hl |
| Country | gl | gl | gl |
| Device | device | type | device (desktop, mobile, tablet) |
| Result Count | num | num | num (up to 100) |
| Offset/Page | start | page | start (0, 10, 20…) |
Testing & Documentation
Postman Collection
Import our official collection to test all endpoints instantly without writing a single line of code.
Developer Docs
Access deep technical parameter guides, JSON schemas, and implementation examples for every engine.
Developer Tools
Playground
zenserp.com/playground (Use this to auto-generate Python/Node.js/CURL snippets).
Batch Requests
For high-volume migrations, use the v2/batch endpoint to submit multiple queries in one call.
Unlimited Concurrency
All paid plans include unlimited concurrency (parallel requests), which is a major shift from SerpApi’s throughput limits.
Request Builder
Quickly construct complex search queries with our visual request builder interface.
Powering the Future of Search Data
Ready to Migrate to Zenserp?
Start sending real-time structured SERP data without infrastructure overhead.
