Snapdeal search · Snapdeal API

GET https://api.api.sh/snapdeal/v1/search

1 credit / call e-commerce try it in the playground →

Snapdeal keyword search (India), 20 per page: id, name, brand, link, price, MRP, discount, rating and image, with every sort, a price range and paging.

Every response includes credits_used: the credits this call cost.

Parameters

name	type	description
`q`required	string	Search words. Example: `shoes`
`sort`	relevance \| price-asc \| price-desc \| discount-desc \| newest	Sort order. Example: `price-asc`
`min_price`	integer	Minimum price.
`max_price`	integer	Maximum price.
`page`	integer	Page number (default 1). `next_page` is null on the last page. Example: `1`

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/snapdeal/v1/search?q=shoes" \
  -H "x-api-key: $APISH_KEY"

import os, requests

res = requests.get(
    "https://api.api.sh/snapdeal/v1/search",
    params={"q": "shoes"},
    headers={"x-api-key": os.environ["APISH_KEY"]},
    timeout=120,
)
res.raise_for_status()
data = res.json()

const url = new URL("https://api.api.sh/snapdeal/v1/search");
url.searchParams.set("q", "shoes");

const res = await fetch(url, { headers: { "x-api-key": process.env.APISH_KEY } });
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const data = await res.json();

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.