Developer basics
API overview
Every Progare store — its catalog, cart, checkout and customer accounts — is served by one REST API. The storefronts Progare hosts use it, and you can use it to build your own frontend, a mobile app, or to connect another website to a store.
Base URL
https://api.progare.comAll requests and responses are JSON over HTTPS. Send Content-Type: application/json on requests with a body.
The store slug
Storefront endpoints are scoped to one store by its slug in the path:
https://api.progare.com/storefront/{storeSlug}/productsGet a slug from the store owner, or resolve it from a domain with GET /stores/resolve-host. Data never crosses stores: a slug only ever returns that store’s products, carts and customers.
Your first request
No key is needed to read a store’s public catalog:
curl "https://api.progare.com/storefront/mahi-studio/products?limit=2&sort=newest"{
"data": [
{
"id": "c1f0…",
"name": "Handblock Cotton Kurta",
"slug": "handblock-cotton-kurta",
"price": "1299.00",
"images": ["https://…/kurta-1.webp"],
…
}
],
"meta": { "page": 1, "limit": 2, "total": 48, "totalPages": 24 }
}What the API covers
| Area | Path prefix | Guide |
|---|---|---|
| Store info, catalog, content, SEO, blog | /storefront/{storeSlug} | Catalog & content |
| Cart, shipping, checkout, payment | /storefront/{storeSlug}/cart, /checkout | Cart & checkout |
| Shopper sign-up, login, account | /storefront/{storeSlug}/auth, /account | Shopper accounts |
| Enquiries, newsletter, order tracking | /storefront/{storeSlug}/enquiry, /newsletter, /track | Forms & enquiries |
| Domain → store, templates | /stores/resolve-host, /templates | Custom storefront |
| AI assistant widget | /assistant-widget/widget.js | Embed the assistant |
Interactive API reference
The full, generated OpenAPI reference — every endpoint, parameter and schema — lives at api.progare.com/docs. Use these guides to understand the flows, and the reference for exact schemas.
Something unclear or out of date? Tell us