amiparis.com APIamiparis.com ↗
Access Ami Paris product data, collections, variants, images, and new arrivals via 8 structured endpoints. Covers pricing, inventory, and catalog browsing.
curl -X GET 'https://api.parse.bot/scraper/05a27e1c-4a24-49c5-a584-2464a895ab5e/get_product?handle=ami-de-coeur-crewneck-sweater' \ -H 'X-API-Key: $PARSE_API_KEY'
Retrieve full product details including variants, pricing, images, and options by product handle.
| Param | Type | Description |
|---|---|---|
| handlerequired | string | Product handle (URL slug), obtainable from search_products or list_collection_products results. |
{
"type": "object",
"fields": {
"product": "object containing id, title, handle, body_html, vendor, product_type, tags, variants (array of size/price objects), options, images (array of image objects with src/dimensions), and image (primary image)"
},
"sample": {
"data": {
"product": {
"id": 15074033238401,
"title": "Black Wool Crewneck Sweater With Contrasted Ami De Coeur",
"handle": "black-wool-ami-de-coeur-crewneck-sweater-uks838018009",
"images": [
{
"id": 81493729116545,
"src": "https://cdn.shopify.com/s/files/1/0774/7865/8352/files/UKS838.018_243bdb5d.jpg",
"width": 2280,
"height": 2850
}
],
"vendor": "Ami Paris",
"options": [
{
"name": "Size",
"values": [
"XXS",
"XS",
"S"
]
}
],
"variants": [
{
"id": 54305078247809,
"sku": "UKS838.018.009",
"price": "580.00",
"title": "XXS",
"available": true
}
],
"body_html": "Sweater in felted merino wool knit."
}
},
"status": "success"
}
}About the amiparis.com API
The Ami Paris API exposes 8 endpoints covering the full amiparis.com product catalog, including collections, variants, images, and search. The get_product endpoint returns a complete product object with variant-level pricing, SKUs, and availability. Developers can also browse the Ami De Coeur signature collection, retrieve new arrivals filtered by gender, and paginate through all store collections — each with product counts and descriptions.
Product and Variant Data
The get_product endpoint accepts a handle (the URL slug) and returns a single product object with fields including id, title, body_html, vendor, product_type, tags, options, and a variants array. Each variant carries price, sku, option1, available, and barcode. The dedicated get_product_variants endpoint surfaces the same variant data with explicit emphasis on size and color breakdown, while get_product_images isolates the images array, giving each image id, src, width, height, alt, and position alongside the primary image object.
Collections and Catalog Navigation
list_collections returns an array of collection objects — each with id, title, handle, description, published_at, updated_at, image, and products_count — and supports page and limit parameters (up to 250 per page). Once you have a collection_handle, pass it to list_collection_products to retrieve all products in that collection with the same pagination controls. The get_ami_de_coeur_collection endpoint is a convenience shortcut specifically for Ami's signature heart-logo line.
Search and Discovery
search_products accepts a query string and returns up to 10 matching products via predictive search. Each result includes id, title, handle, price, image, url, body, available, and vendor. The get_new_arrivals endpoint retrieves recently added products and accepts an optional gender parameter ('men' or 'women'); omitting it returns all new arrivals regardless of gender category.
Handle-Based Addressing
Most single-resource endpoints (get_product, get_product_variants, get_product_images) require a handle rather than a numeric ID. Handles are returned in the handle field of any product object from search_products, list_collection_products, or get_new_arrivals, so a typical workflow starts with a collection or search call to collect handles before fetching full product details.
- Build a price-tracker for Ami Paris items by polling
get_productfor variant-levelpriceandavailablefields. - Sync the full Ami Paris catalog to an internal database using
list_collectionsfollowed bylist_collection_productswith pagination. - Power a gender-filtered new-arrivals feed using
get_new_arrivalswith thegenderparameter set to'men'or'women'. - Display size and color availability grids by fetching variant data via
get_product_variantsfor a given product handle. - Populate a lookbook or editorial page with high-resolution image metadata from
get_product_images, includingwidth,height, andaltfields. - Implement a site search autocomplete by querying
search_productswith a keyword and returning up to 10 product results with prices and images. - Scope a dataset to the Ami De Coeur line specifically using
get_ami_de_coeur_collectionwithout needing to know the collection handle.
| 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 | 250 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.
Does Ami Paris have an official public developer API?+
What does `search_products` return, and how does it differ from `list_collection_products`?+
search_products accepts a free-text query and returns up to 10 results via predictive search. Each result includes price, url, available, and vendor fields but is limited to 10 items and does not support pagination. list_collection_products requires a collection_handle and supports paginated browsing of up to 250 items per page, making it more suitable for bulk catalog access.Does the API expose customer reviews or ratings for products?+
Are there any limitations on pagination across collection endpoints?+
list_collections and list_collection_products both accept page (integer) and limit (up to 250) parameters. search_products does not support pagination and caps results at 10. If you need full catalog coverage, use list_collection_products with incremented page values until a page returns fewer results than the requested limit.Does the API include sale pricing, discount codes, or promotional data?+
price field, but sale prices, compare-at prices, discount codes, and promotion details are not exposed as dedicated response fields. You can fork the API on Parse and revise it to surface compare_at_price from the variant object if that data is available in the source.