Deprecated

Legacy API v0

This page documents the legacy v0 endpoints (/api/search and /api/url) that have been replaced by API v1. The v0 endpoints remain operational for backwards compatibility but will be permanently shut down on December 31, 2026 23:59 UTC.

TL;DR — Drop-in migration

v1 is a drop-in replacement. Same JSON body, same authentication header, same response shape. Just add /v1 to the path.

Legacy (v0)	Current (v1)	Purpose
`/api/search`	`/api/v1/search`	Google / Bing SERP (organic results, ads, knowledge graph)
`/api/url`	`/api/v1/url`	Reader API — URL → Markdown / HTML / screenshots / PDF parsing

See all v1 APIs → Test v1 in Playground

Deprecation timeline

Now — May 2026

v1 endpoints are live and stable. v0 endpoints remain fully operational; existing integrations continue to work without changes.
Mid-2026

New features (e.g. YouTube Search API, File Extraction API) will ship on v1 only. v0 will not receive new fields or parameters.
December 31, 2026 23:59 UTC

v0 endpoints will be permanently removed. Requests to /api/search and /api/url will no longer succeed.

Legacy endpoint reference

Kept for backwards reference only. Do not build new integrations against these endpoints.

POST https://www.searchcans.com/api/search Legacy

Legacy SERP endpoint. Replaced by /api/v1/search.

View Python example (deprecated)

# DEPRECATED — endpoint will be removed on December 31, 2026 23:59 UTC
import requests

response = requests.post(
    'https://www.searchcans.com/api/search',  # use /api/v1/search instead
    headers={
        'Authorization': 'Bearer YOUR_API_KEY',
        'Content-Type': 'application/json'
    },
    json={'s': 'artificial intelligence', 't': 'google'}
)
results = response.json()['data']

POST https://www.searchcans.com/api/url Legacy

Legacy Reader endpoint. Replaced by /api/v1/url.

View Python example (deprecated)

# DEPRECATED — endpoint will be removed on December 31, 2026 23:59 UTC
import requests

response = requests.post(
    'https://www.searchcans.com/api/url',  # use /api/v1/url instead
    headers={
        'Authorization': 'Bearer YOUR_API_KEY',
        'Content-Type': 'application/json'
    },
    json={'s': 'https://example.com', 't': 'url', 'w': 3000}
)
markdown = response.json()['data']['markdown']

Migration FAQ

Does my code need to change beyond the URL path? ▾

No. The request body, authentication header (Bearer YOUR_API_KEY), and response JSON shape are identical between v0 and v1. The only required change is the URL: replace /api/search with /api/v1/search, and /api/url with /api/v1/url.

Is my API key the same? ▾

Yes. The same API key authenticates both v0 and v1 requests. Credit balances, Parallel Lanes, and rate limits are shared across versions.

Will v0 still bill credits during the deprecation window? ▾

Yes. Requests against v0 endpoints continue to consume credits at the same rate as v1 until December 31, 2026 23:59 UTC. After that date, requests will simply fail.

Will new features ship to v0? ▾

No. New parameters, response fields, and product APIs (e.g. YouTube Search, File Extraction) ship on v1 only. v0 is in maintenance mode.

What happens after December 31, 2026 23:59 UTC? ▾

The v0 endpoints will be permanently removed. Requests to /api/search and /api/url will no longer return successful responses. Make sure all integrations are migrated before that date.

Migrate to API v1 today

Same key, same payload, same response — just add /v1 to the path. Drop-in replacement, zero downtime.

Browse v1 APIs → Try in Playground