Redirects API reference
Reference map for Redirects API operations.
- Updated
- Apr 26, 2026
Redirects
Use the section that matches your caller: storefront clients use Shopper REST or Search, trusted services use Management, and signed-in customer flows use Auth. Prefer Search API for new discovery-heavy storefront work.
Use Redirects when the job is resolving old slugs or administering redirect records for catalog items.
Shopper API redirect reads resolve redirects by old slug or item ID for storefront/runtime lookup. Management API redirect operations own app-wide listing, item-scoped listing, reads by ID, creation, updates, deletion, and deleting all redirects for an item.
Use Products, Categories, Collections, or Brands when the underlying catalog record is changing. Use Redirects when preserving navigation from an old route to an existing item.
For workflow guidance across storefront redirect reads, trusted redirect administration, product relations, smart listings, static listings, Search, and events, see Redirects, relations, and listings.
Shopper API · read
Read and inspect
| Operation | API |
|---|---|
| Fetch redirects | Shopper API |
| Fetch redirects by item ID | Shopper API |
| Fetch redirects by old slug | Shopper API |
Management API · read, create, update, and remove
Read and inspect
| Operation | API |
|---|---|
| Get redirect by ID | Management API |
| List all app redirects | Management API |
| List redirects for an item | Management API |
Create or attach
| Operation | API |
|---|---|
| Create a new redirect | Management API |
Update or repair
| Operation | API |
|---|---|
| Update a redirect | Management API |
Remove or deactivate
| Operation | API |
|---|---|
| Delete a redirect | Management API |
| Delete all redirects for an item | Management API |