Web Reader
Turn a public web page into usable Markdown, metadata, and HTML.
Fields: title, description, markdown, html
SERPpost V1
SERPpost V1 is a JSON API for Google and Bing result types plus public-page capture. Send an authenticated POST request, choose the result shape you need, and pass the returned fields into your own workflow.
Start here
Register, then open your Dashboard to access your API key.
Use Search for result sets. Use Reader after you already have a public URL.
Validate a request in the Playground before placing the key in a backend job or worker.
POST /api/v1/search
Set t to the result type your application needs. Result fields can vary by query, so parse only the fields your workflow uses.
| Result type | t value | Response fields to inspect |
|---|---|---|
| Google Search | google | organic, relatedSearches, aiOverview |
| Google Shopping | google_shopping | shopping_results |
| Google Images | google_images | images_results, suggestedSearches |
| Google News | google_news | news_results |
| Google Videos | google_videos | video_results |
| Google Short Videos | google_short_videos | short_video_results |
| Bing Search | bing | organic |
curl -X POST https://serppost.com/api/v1/search \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"s": "web to markdown api",
"t": "google",
"p": 1,
"d": 20000,
"country": "us",
"language": "en",
"maxCache": 0
}' POST /api/v1/url
Reader starts with a publicly accessible URL. The base request returns page metadata and readable content. Add the file or screenshot option when your source calls for it.
Turn a public web page into usable Markdown, metadata, and HTML.
Fields: title, description, markdown, html
Extract readable content from a publicly accessible document URL.
Fields: title, description, fileUrl, fileMarkdown
Add file: 1.
Capture a rendered page alongside machine-readable content.
Fields: title, description, markdown, imageUrl
Add mode: 1 and image: 1.
curl -X POST https://serppost.com/api/v1/url \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"s": "https://example.com/article",
"t": "url",
"w": 3000,
"d": 20000,
"html": 1,
"proxy": 0,
"maxCache": 0
}' Response envelope
A successful request returns code: 0. When the code is non-zero, handle the message before you try to parse the response data.
{
"code": 0,
"msg": "",
"data": {
"id": "request-id",
"organic": []
}
} Production notes
maxCache: 0 so you can inspect a live request. Decide cache, retry, and storage behavior in your own production workflow.proxy: 0 and html: 1. Test public source URLs before scheduling batch work.FAQ
V1 supports Google Search, Bing Search, Google Shopping, Google Images, Google News, Google Videos, and Google Short Videos. Choose the result type with the t parameter.
Use the reader endpoint after you have a public URL and need page metadata, Markdown, HTML, document content, or a screenshot. It is separate from the search endpoint.
The Playground is for validating a live request, so it sends maxCache: 0. In production, choose cache behavior deliberately for your workload and keep your own storage and retry policy.
Request Slots are the number of live API requests your account can run at the same time. Your Dashboard shows the current value for your account.