Account created on 16 November 2022, over 2 years ago
#

Recent comments

Hello!

I installed the library from wirecutter https://github.com/thewirecutter/paapi5-php-sdk, but the errors from the top comment remained

Ways to reproduce:
1. Install the module and add the credentials in the configurations
2. Installed the library from https://github.com/thewirecutter/paapi5-php-sdk, renamed it to amazon_sdk, and replaced the credentials in the library

Hello, thank you for the quick response.

I installed the dev version of the module and encountered similar errors as in the previous comment.

Here are the errors:

Error calling PA-API 5.0! [401] Client error: POST https://webservices.amazon.com/paapi5/getitems resulted in a 401 Unauthorized response: {"__type":"com.amazon.paapi5#InvalidSignatureException","Errors":[{"Code":"InvalidSignature","Message":"The request has (truncated...)

Error: The request has not been correctly signed. If you are using an AWS SDK, requests are signed for you automatically; otherwise, go to this link.

User warning: Invalid placeholder (!link) with string: "%input is no valid ASIN. Please check the !link for messages." in Drupal\Component\Render\FormattableMarkup::placeholderFormat() (line 246 of /var/www/web/core/lib/Drupal/Component/Render/FormattableMarkup.php).

I would appreciate your help.

Thank you!

Hello again,

I enabled API requests and received the following errors when sending a test request:

Error: The request has not been correctly signed. If you are using an AWS SDK, requests are signed for you automatically; otherwise, go to this link.

Error calling PA-API 5.0! [401] Client error: POST https://webservices.amazon.com/paapi5/getitems resulted in a 401 Unauthorized response: {"__type":"com.amazon.paapi5#InvalidSignatureException","Errors":[{"Code":"InvalidSignature","Message":"The request has (truncated...)

Although the keys are correctly created, and I have installed the amazon_sdk library from this link: https://github.com/thewirecutter/paapi5-php-sdk. I also replaced all access, secret keys, and partner tags in the library.

Thank you for your response.

I've encountered the same problem as coaston, is there a solution?

The problem is that jsonapi_site.routing.yml has requirements : _user_is_logged_in: 'TRUE' , which blocks an anonymous user. I tried to remove this option and replace it with _permission: 'access content', but it did not solve the problem. Please update

Production build 0.71.5 2024