SERPpost V1

Search the web. Capture the page. Keep the response usable.

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

Make one authenticated V1 request

  1. 1. Create an account

    Register, then open your Dashboard to access your API key.

  2. 2. Pick a response type

    Use Search for result sets. Use Reader after you already have a public URL.

  3. 3. Test, then move server-side

    Validate a request in the Playground before placing the key in a backend job or worker.

POST /api/v1/url

Page and file capture

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.

Web Reader

Turn a public web page into usable Markdown, metadata, and HTML.

Fields: title, description, markdown, html

File Extraction

Extract readable content from a publicly accessible document URL.

Fields: title, description, fileUrl, fileMarkdown

Add file: 1.

Web Screenshot

Capture a rendered page alongside machine-readable content.

Fields: title, description, markdown, imageUrl

Add mode: 1 and image: 1.

Web Reader request

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

Check code before reading data

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

Keep keys private and requests deliberate

  • Keep the Bearer token in your server-side environment. Do not ship it in a public browser bundle.
  • The Playground sends maxCache: 0 so you can inspect a live request. Decide cache, retry, and storage behavior in your own production workflow.
  • Reader examples use proxy: 0 and html: 1. Test public source URLs before scheduling batch work.
  • Your Dashboard shows credits and the number of Request Slots currently available to your account.

FAQ

Common integration questions

Which V1 search result types are available?

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.

When should I use the reader endpoint?

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.

Why does every Playground request use maxCache: 0?

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.

How do Request Slots affect my integration?

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.