Weave Code
Laravel Amazon Product Api Laravel Package
revolution/laravel-amazon-product-api
Laravel package for integrating the Amazon Product Advertising API. Search products, look up details by ASIN, and retrieve pricing, images, and metadata through a simple, configurable client with Laravel-friendly setup.
Amazon Product Advertising API for Laravel
Frequently asked questions about Laravel Amazon Product Api
- What does revolution/laravel-amazon-product-api actually do?
- It is a thin Laravel service-provider wrapper around Amazon's Product Advertising API 5.0. It provides a config file for your credentials, an AmazonProduct facade, a Guzzle-based client handling AWS Signature V4, and a small fluent request builder. You use it to look up items by ASIN and run product searches against Amazon's catalog.
- How do I install and configure this package in Laravel?
- Install it with Composer and publish the package config file, typically config/amazon-product.php, then fill in your Amazon access key, secret key, partner tag, and marketplace or region. Configuration is done once and the facade picks it up through the service provider. Check the exact tag's composer.json first, because the 4.2.0 release changed PHP and Laravel version floors.
- Which PHP and Laravel versions does the package support?
- Release 4.2.0 explicitly drops PHP 7.1 and Laravel 5.8, so older stacks are out of scope. The changelog wording is ambiguous about whether the floors were raised to a modern PHP 8.x and Laravel 10+ set, so read the composer.json in the exact tag rather than trusting release notes. Pin the version you evaluate and verify constraints directly.
- What Amazon credentials and account do I need to use it?
- You need an approved Amazon Associates account with Product Advertising API access, plus an access key, secret key, and partner tag for each marketplace you target. PA-API access requires qualifying sales activity, so approval is a business gate that must clear before development starts. No amount of code work makes the package function without that eligibility.
- How do I search products or look up a single ASIN with this package?
- Calls go through the AmazonProduct facade using the fluent builder, for example AmazonProduct::item()->withId('ASIN')->withResources([...])->fetch(). Searches use the search operation with keyword and filter parameters. The withResources call is important because it selects which data blocks, such as pricing, images, or metadata, come back from Amazon.
- Is this package still maintained, and should I depend on it in production?
- Release 4.2.0 declares end of active support, so there will be no further bugfixes, security patches, or responses to Amazon API changes. Most dependency policies bar unpatched third-party code, which makes requiring it from Packagist problematic regardless of technical fit. The safer route is to treat it as a reference implementation and vendor or fork the signing and endpoint logic you need.
- How do I test code that uses this package, given it wires Guzzle directly?
- Because the client is built on Guzzle rather than Laravel's HTTP client, Http::fake() will likely not intercept its requests. Expect to hand-roll mocks around the Guzzle client or wrap the package behind your own adapter interface. If the client accepts an injected Guzzle instance, that makes both testing and instrumentation significantly easier.
- Does the package handle retries, rate limiting, or caching?
- No. There is no built-in retry or backoff logic, no rate limiter, and no response caching, so all of that is your responsibility. Amazon also imposes price caching freshness rules of roughly 24 hours and requires timestamps and attribution in displayed data. The package offers no compliance guardrails, so you must implement throttling and cache policy yourself.
- Are there alternatives to using this package for Amazon product data?
- You can call PA-API 5.0 directly with the official AWS SDK or a maintained signing library, which avoids an abandoned dependency entirely. Forking this package's SigV4 signing logic and marketplace endpoint map is a practical middle path, since those are only a few hundred lines. Third-party data providers exist as well, but they carry their own cost and licensing terms.
- What are the biggest risks before adopting this package?
- The top risk is eligibility: without an approved Associates account, nothing works. Next is abandonment, now confirmed as declared end of life with no security patching, combined with a breaking version-floor bump in the same release. Compliance with Amazon's licensing for cached prices and images, plus the absence of retry and rate limiting, are operational gaps you must close yourselves.
Weaver
How can I help you explore Laravel packages today?