Retail pricing and sale monitoring
Use Macy's endpoints to turn retail pricing and sale monitoring into repeatable API requests with documented inputs and JSON responses.
Turn a Macy's product page into structured retail data — name, brand, department/division, category breadcrumb, sale-aware pricing, availability, images, aggregate rating, and every purchasable color variant with its own price, all as normalized JSON. Credential-free.
Get full Macy's product detail — pricing with sale detection, availability, images, ratings, and every color variant's own price — as structured JSON.
Endpoint families
1
Documented params
2
Examples
0
Live catalog snapshot
Active endpoints
1
Methods
GET
Required params
2
Schema refs
1
{
"platform": "Macy's",
"endpoint": "macys-product",
"method": "GET",
"path": "/macys/product/{productId}",
"auth": "apiKey"
}Use cases
Get full Macy's product detail — pricing with sale detection, availability, images, ratings, and every color variant's own price — as structured JSON.
Use Macy's endpoints to turn retail pricing and sale monitoring into repeatable API requests with documented inputs and JSON responses.
Use Macy's endpoints to turn product catalog research into repeatable API requests with documented inputs and JSON responses.
Use Macy's endpoints to turn color-variant price tracking into repeatable API requests with documented inputs and JSON responses.
Managed execution
Each Crawlora platform API is designed around a specific data surface. Instead of exposing a generic fetch endpoint, Crawlora combines endpoint-specific request logic, managed infrastructure, parsing, normalization, billing, and Playground-tested examples.
Request behavior is tuned for the target platform and endpoint type.
Supported endpoints can use managed proxy routing to improve reliability and reduce infrastructure work.
Dynamic pages can be routed through managed browser instances where JavaScript rendering is required.
Challenge pages and unusable upstream responses are detected and surfaced clearly.
Results are returned as documented JSON instead of raw HTML.
Test the same route from Docs and Playground before production integration.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/macys/product/{productId}
Endpoint catalog
/macys/product/{productId}Returns one Macy's product's full detail: name, brand, description, department/division, category breadcrumb, pricing (with sale detection), availability, images, aggregate rating, and every purchasable color variant with its own price. productId is a numeric id, taken from a Macy's product page's ?ID= query parameter.
Related APIs
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
Marketplaces & Retail
Turn public Shop.app product and merchant pages into structured JSON for e-commerce product intelligence, price research, shop monitoring, and marketplace discovery workflows.
How to scrape Macy's
Crawlora's Macy's endpoint returns full product detail as normalized JSON with one API key — no Macy's account required.
Macy's doesn't expose a search or category-listing endpoint — take the numeric productId from a Macy's product page's ?ID= query parameter.
Pass that productId to /macys/product/{productId} for the product's full detail: sale-aware pricing, availability, images, aggregate rating, and every purchasable color variant's own price.
FAQ
Not directly — Crawlora's Macy's coverage is product-detail only (/macys/product/{productId}), with no search or category-listing endpoint yet. Source productId values from Macy's product page URLs (the numeric ?ID= query parameter) rather than from a Crawlora search call.
Yes — /macys/product/{productId} returns sale-aware pricing alongside availability, images, an aggregate rating, and every purchasable color variant with its own price.