India Handmade APIindiahandmade.com ↗
Access the full directory of registered artisans on India's official handloom and handicraft marketplace. List sellers with pagination or fetch detailed profiles.
What is the India Handmade API?
The India Handmade API provides 2 endpoints to access the seller directory on indiahandmade.com, the Government of India's marketplace for handloom and handicraft artisans. The list_sellers endpoint returns paginated results with each seller's name, shop slug, product count, and URLs, while get_seller_profile delivers individual seller details including location, star rating, about text, and banner image.
curl -X GET 'https://api.parse.bot/scraper/179e49c8-61d9-4621-bd1e-4bf98b872656/list_sellers?page=1&limit=4&category=bed-linen-cushions' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns a paginated list of marketplace sellers. Without a category filter, returns all registered sellers from the seller directory (1798+ sellers, ordered by most recently registered first). With a category filter, returns unique sellers who have products listed under that category by fetching product pages in the category and extracting seller info. Category-filtered results require multiple upstream requests (one per product page until limit unique sellers are found), so response time scales with the limit. Use the page parameter to paginate through all sellers when no category is specified.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination (1-indexed). |
| limit | string | Number of sellers per page. |
| category | string | Category slug or URL path to filter sellers by product category. Accepts a category slug (e.g. 'bed-linen-cushions', 'home-and-living') or a full category path (e.g. 'home-and-living/bed-linen-cushions'). When provided, returns only sellers who have products listed under that category. Omitting returns all sellers regardless of category. |
{
"type": "object",
"fields": {
"page": "current page number",
"limit": "results per page",
"total": "total number of sellers (all sellers when unfiltered, found sellers count when category-filtered)",
"sellers": "array of seller objects with name, shop_slug, product_count, profile_url, collection_url, logo_url",
"category": "resolved category display name, present only when category filter is used"
},
"sample": {
"data": {
"page": 1,
"limit": 16,
"total": 1798,
"sellers": [
{
"name": "SWASTIK MAHILA UDYOG SAHAKAR SAMITI",
"logo_url": "https://img.indiahandmade.com/avatar//crop6a74b0592681b.jpg",
"shop_slug": "SWASTIK MAHILA UDYOG SAHAKAR SAMITI",
"profile_url": "https://www.indiahandmade.com/marketplace/seller/profile/shop/SWASTIK MAHILA UDYOG SAHAKAR SAMITI",
"product_count": 3,
"collection_url": "https://www.indiahandmade.com/marketplace/seller/collection/shop/SWASTIK MAHILA UDYOG SAHAKAR SAMITI"
}
]
},
"status": "success"
}
}About the India Handmade API
Seller Directory Access
The list_sellers endpoint returns a paginated list of every registered seller on India Handmade. Each result includes the seller's name, shop_slug, product_count, profile_url, collection_url, and logo_url. The total field in the response lets you calculate page counts and build full pagination flows using the page and limit input parameters. Results follow the site's default ordering.
Detailed Seller Profiles
The get_seller_profile endpoint accepts a shop_slug (obtained from list_sellers) and returns a fuller picture of a single seller. The response includes name, about text (nullable), a rating out of 5 (nullable), a location string with city, state, pincode, and country, logo_url, banner_url (nullable), and both profile_url and collection_url. This makes it straightforward to build a seller detail view or enrich a directory listing.
Coverage and Scope
Both endpoints cover all sellers registered on indiahandmade.com, a platform run under the Government of India's Ministry of Textiles. The directory spans handloom weavers, handicraft artisans, and cooperatives. Individual product listings, order data, and transaction history are not part of this API — only seller identity and profile metadata are returned.
The India Handmade API is a managed, monitored endpoint for indiahandmade.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when indiahandmade.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 indiahandmade.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 searchable directory of Government of India-registered artisans using seller name, location, and rating fields.
- Display seller profile cards with logo, banner image, and about text sourced from get_seller_profile.
- Track total registered artisan count over time using the total field from list_sellers.
- Map artisan distribution across Indian states using the location field from seller profiles.
- Filter or rank sellers by star rating to surface highly-rated craftspeople.
- Sync a local database of artisan shop slugs and product counts using paginated list_sellers calls.
- Power an affiliate or discovery site linking to artisan collection_url pages on India Handmade.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.