Discover/NuviaDZ API
live

NuviaDZ APINuviadz.store

Access NuviaDZ store product data via 3 endpoints. Search products, list categories, and fetch detailed product info including price, images, and description.

This API takes change requests — .
Endpoint health
verified 1h ago
list_categories
get_product
search_products
3/3 passing latest checkself-healing
Endpoints
3
Updated
2h ago

What is the NuviaDZ API?

The NuviaDZ Store API exposes 3 endpoints for reading product and category data from the Nuviadz.store online shop. The search_products endpoint accepts a keyword query and returns paginated results with titles, prices, images, and slugs. The get_product endpoint returns structured detail including numeric price, currency code, HTML description, badge labels, and multiple images for any individual product.

This call costs1 credit / call— charged only on success
Try it
Page number for pagination.
Search keyword to find products.
Sort order for results. Omitted returns default store ordering.
api.parse.bot/scraper/04dda19c-891c-4651-b6ad-8b3243196c9c/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/04dda19c-891c-4651-b6ad-8b3243196c9c/search_products?query=oreille' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace nuviadz-store-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""Walkthrough: NuviaDZ Store SDK — browse categories, search, and drill into product details."""
from parse_apis.nuviadz_store_api import NuviaDZ, SortBy, ProductNotFound

client = NuviaDZ()

# Browse all store categories.
for category in client.categories.list(limit=10):
    print(category.name, category.url)

# Search products by keyword, sorted by price ascending.
hit = client.product_summaries.search(query="oreille", sort_by=SortBy.PRICE_ASC, limit=5).first()

# Drill into the full product detail from the search hit.
if hit is not None:
    product = hit.details()
    print(product.title, product.price, product.currency)
    print("Images:", product.images)
    print("Badges:", product.badges)

    # Point-lookup by slug discovered from the search result.
    try:
        same = client.products.get(slug=product.slug)
        print(same.title, same.price_display)
    except ProductNotFound:
        print("Product no longer available")

print("exercised: categories.list / product_summaries.search / details / products.get")
All endpoints · 3 totalmissing one? ·

Search for products by keyword. Returns matching products with title, price, image, and product slug. Supports sorting by price, date, or name. Results are paginated; each page returns the products the store renders for that page number. An unmatched query returns an empty products array.

Input
ParamTypeDescription
pageintegerPage number for pagination.
queryrequiredstringSearch keyword to find products.
sort_bystringSort order for results. Omitted returns default store ordering.
Response
{
  "type": "object",
  "fields": {
    "page": "current page number",
    "query": "the search query echoed back",
    "sort_by": "sort option used, or null if default",
    "products": "array of product objects with slug, url, title, price, compare_price, and image"
  },
  "sample": {
    "data": {
      "page": 1,
      "query": "oreille",
      "sort_by": null,
      "products": [
        {
          "url": "https://nuviadz.store/products/oreille",
          "slug": "oreille",
          "image": "https://cdn.youcan.shop/stores/af046447d182987209d25d1e9fab5c4b/products/EDU0qxEBjZHzxGIE8t6grT9MixQrJQuBkwuSPwO4_md.jpg",
          "price": "‏٢٬٥٠٠ د.ج",
          "title": "Oreille CANADA",
          "compare_price": null
        }
      ]
    },
    "status": "success"
  }
}

About the NuviaDZ API

Endpoints Overview

The API covers three operations against the NuviaDZ store catalog. search_products takes a required query string and optional page integer and sort_by parameter, returning an array of product objects. Each product object in results carries slug, url, title, price, compare_price, and image. The sort_by field accepts ordering by price, date, or name; omitting it returns the store's default ordering. An unmatched query returns an empty products array.

Product Detail

get_product accepts a slug string — the same value returned in search_products results — and returns a single product's full record. Response fields include title, description, description_html, price (numeric), price_display (formatted with currency symbol), currency (ISO code, e.g. DZD), images (array of URLs), and badges (array of label strings such as new or discount). When the slug doesn't match any product, the endpoint returns an input_not_found response.

Categories

list_categories takes no inputs and returns all product collections available in the store. Each category object includes slug, name, url, and image. The store currently maintains a small, fixed set of categories, so this endpoint is suitable for building navigation or filter menus rather than dynamic category discovery.

Reliability & maintenanceVerified

The NuviaDZ API is a managed, monitored endpoint for Nuviadz.store — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when Nuviadz.store 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 Nuviadz.store 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.

Last verified
1h ago
Latest check
3/3 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Build a product search widget that queries NuviaDZ by keyword and displays titles, prices, and thumbnails.
  • Track price changes on specific products by polling get_product with a known slug and recording the numeric price field over time.
  • Render a category navigation menu using slugs, names, and images from list_categories.
  • Detect discounted products by checking compare_price against price in search_products results.
  • Display badge labels (new, discount) from get_product to highlight promoted items in a third-party storefront.
  • Paginate through all search results for a keyword by incrementing the page parameter and collecting product slugs.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 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.

Frequently asked questions
Does Nuviadz.store have an official developer API?+
Nuviadz.store does not publish an official public developer API or developer documentation.
What currency does the API return prices in?+
get_product returns a currency field with an ISO code — the store uses DZD (Algerian Dinar). The price field is numeric, and price_display is the formatted string with the currency symbol. search_products results also include price and compare_price per product.
Does `search_products` support filtering by category or price range?+
The endpoint supports sorting via sort_by (price, date, or name) and pagination via page, but does not currently accept a category filter or price-range parameter. If you need category-scoped search, you can fork this API on Parse and revise it to add those input parameters.
Are product reviews or stock availability returned?+
Not currently. The API covers product titles, prices, descriptions, images, and badge labels. Stock availability and customer reviews are not included in any endpoint response. You can fork the API on Parse and revise it to add an endpoint covering those fields if the store surfaces them.
What happens when I request a slug that doesn't exist?+
get_product returns an input_not_found response when the provided slug does not match any product in the store. Slugs should be taken directly from the slug field in search_products results to avoid this.
Page content last updated . Spec covers 3 endpoints from Nuviadz.store.
Related APIs in EcommerceSee all →