notonthehighstreet APInotonthehighstreet.com ↗
Access products, sellers, reviews, and categories from notonthehighstreet.com via a structured API. Search listings, fetch product details, and browse by category.
What is the notonthehighstreet API?
This API covers notonthehighstreet.com across 8 endpoints, giving programmatic access to product listings, seller profiles, customer reviews, category browsing, and search suggestions. The get_product_details endpoint returns over a dozen fields per product including pricing, variant options, HTML description, availability, and image URLs — enough to build a full product page without any supplementary requests.
curl -X GET 'https://api.parse.bot/scraper/41ef3ecc-2511-4869-b2e8-58ffc4e69d8f/search_products?page=1&sort=newest&query=personalised+gifts&page_size=60' \ -H 'X-API-Key: $PARSE_API_KEY'
Full-text search over the marketplace product catalog. `query` matches product titles and descriptions; results are paginated with configurable page size. Returns product summaries with pricing, seller info, and availability. Omitting query returns all products. Each ProductSummary includes seller_slug and product_slug for navigating to full details.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number. |
| sort | string | Sort order. Accepted value: 'newest'. Only applied on page 1 via SSR fallback. |
| query | string | Search keyword (e.g. 'personalised gifts'). Omitting returns all products. |
| page_size | integer | Results per page. |
{
"type": "object",
"fields": {
"facets": "array of facet objects with key, dynamicFacet, and values",
"metadata": "object containing attributionToken",
"products": "array of product summary objects with title, price, partner, images, code, seller_slug, product_slug",
"pagination": "object with currentPage, totalPages, offset, pageSize, resultsReturnedThisPage, totalResults"
}
}About the notonthehighstreet API
Product and Search Data
The search_products endpoint accepts a query string, page, page_size, and an optional sort parameter (accepted value: newest). Responses include a products array with title, price, partner, images, code, and availability, alongside a facets array and a pagination object carrying totalResults, totalPages, currentPage, and pageSize. The get_search_suggestions endpoint takes a partial query and returns both searchTerms suggestions and partners suggestions — useful for autocomplete UIs.
Product Detail and Reviews
get_product_details requires a seller_slug and a product_slug (both drawn from the product URL). It returns the full product record: title, price (with currency, amount, and exponent), images, options for variants, a detailed attributes object, an HTML description, and an availability string. Complementary endpoints get_product_reviews and get_similar_products accept a numeric product_code. Reviews come back with per-review rating, date, comment, and any seller response, plus aggregate averageProductRating and numberOfReviews.
Sellers and Categories
get_seller_profile returns a partner object with name, id, startDate, storySummary, storyText, logo, coverImage, and location data — enough to render a full seller page. get_seller_products lists that seller's full catalogue with pagination. For category browsing, get_category_products accepts a category_path string (e.g. gifts/gifts-for-her) and returns products alongside facets and pagination metadata, mirroring the search response shape.
The notonthehighstreet API is a managed, monitored endpoint for notonthehighstreet.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when notonthehighstreet.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official notonthehighstreet.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a personalised gift recommendation engine using
search_productsquery results filtered by facets - Aggregate seller profiles and product counts to create a directory of independent UK makers
- Monitor product availability and price fields from
get_product_detailsfor price-tracking tools - Display customer sentiment dashboards using
averageProductRatingand review counts fromget_product_reviews - Power an autocomplete search bar using the
searchTermssuggestions fromget_search_suggestions - Populate a category landing page with facet-filtered product listings via
get_category_products - Surface related items in a gift-finder app using
get_similar_productsrecommendations
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does notonthehighstreet.com offer an official developer API?+
What does `get_product_details` return beyond basic listing data?+
get_product_details returns the full product record for a single item: title, price (with currency, amount, exponent), all images, options (variant choices), an attributes object, an HTML description string, and an availability status. You need both the seller_slug and product_slug from the product's URL to call it. The search and category endpoints return a lighter product shape without the full attributes or description.How does pagination work across endpoints?+
search_products, get_seller_products, get_category_products) use an integer page parameter. Responses include a pagination object with currentPage, totalPages, and totalResults. get_product_reviews also paginates via page and per_page, and its pagination object includes totalEntries and totalPages.Does the API cover order history, wishlists, or checkout data?+
Can I filter search results by price range or other facets?+
search_products endpoint returns a facets array in the response — each facet has a key and available values — but the endpoint inputs only accept query, page, page_size, and sort. Passing facet filters as query parameters is not currently supported. You can fork the API on Parse and revise the endpoint to add facet filter parameters.