ASA2 1.31.0 is now available. This release adds support for the new Amazon Creators API v3 credentials using Login with Amazon (LWA) authentication, fixes keyword caching behavior, and corrects the statistics graph timezone handling.

Creators API v3 Credentials (LWA)

Starting in February 2026, Amazon began issuing a new type of Creators API credentials. These v3 credentials use Login with Amazon (LWA) for authentication instead of Amazon Cognito, which the original v2 credentials use.

If you recently obtained Creators API credentials and encountered an invalid_client error when connecting, your credentials are likely v3. ASA2 1.31 adds full support for these new credentials.

New Credential Type Selector

When adding or editing marketplace credentials under ASA2 > Setup > Amazon Creators API, a new Credential Type dropdown appears in the form. It offers two options:

• Cognito (v2): For existing credentials issued before February 2026
• LWA (v3): For new credentials issued since February 2026

Select the credential type that matches when your credentials were issued.

The API version is determined automatically based on your credential type and marketplace region. Cognito credentials use API versions 2.1–2.3, while LWA credentials use versions 3.1–3.3. There is no need to select the version manually.

Updated Marketplace Table

The configured marketplaces table now includes a Credential Type column between Status and API Version. This makes it easy to see which authentication method each marketplace uses at a glance.

The marketplace table now shows the credential type for each entry.

How to Tell if You Have v3 Credentials

• Before February 2026: Your credentials are almost certainly v2 (Cognito)
• Since February 2026: Your credentials are likely v3 (LWA)
• Getting invalid_client: Edit your marketplace and switch to LWA (v3)

Existing v2 credentials continue to work without changes. For the full setup guide, see the Creators API Setup documentation.

SDK Update

The embedded Amazon Creators API SDK has been updated from v1.0.0 to v1.2.0. Besides the v3 credential support, the updated SDK includes improved rate limiting for HTTP 429 responses.

Keyword Caching and Preload Improvements

Several changes improve how ASA2 handles keyword data and the preload cronjob.

Stale Cache Fix

When an API error response was returned for a keyword search, ASA2 previously stored that error in the cache. After the cache expired, the stale “not available” data persisted until a successful API response replaced it. ASA2 1.31 no longer caches error responses, so keyword results recover correctly after temporary API issues.

Atomic Cache Refresh

The keywords preload cronjob now uses atomic cache refresh. When an API call fails during preload, the existing valid cache entry is preserved instead of being deleted. This prevents situations where a temporary API error would leave keyword results empty until the next successful refresh.

Preload Status Reporting

The keywords preload cronjob now reports accurate success and failure counts after each run. Individual item failures are logged separately, making it easier to identify which keyword configurations have issues. This is especially useful in combination with the new logging channels described below.

Keywords Advanced Logging

Two new logging channels have been added for diagnosing keyword-related issues: asa2-keywords-preload and asa2-keywords-cache. These channels are available through the ASA2 Advanced Log add-on plugin and help trace keyword search requests, cache behavior, and preload cronjob activity. For background on keyword preloading, see the Keywords Cronjob documentation.

Bug Fixes and Improvements

• Statistics graph timezone: The API Request Stats chart on the Dashboard previously used UTC-based rolling time windows. The “Today” view (formerly “Last 24 hours”) now shows the current calendar day in the WordPress timezone, and the 7-day and 30-day views group data by calendar days in that timezone.
• Product Picker error display: When content loading failed in the Product Picker, the literal string “content.text” was displayed instead of the actual error message. This is now fixed.
• Activation error: A fatal error on plugin activation caused by an undefined function in the License Repository has been resolved.

Technical Requirements

• PHP: 8.1 or higher
• WordPress: 5.2 or higher
• Tested up to: WordPress 6.9.1

This update is backward compatible. Existing Creators API configurations using v2 credentials are not affected. No configuration changes are required after updating.

Getting Started

1. Update ASA2 through the WordPress dashboard or download the latest version from your account area
2. If you have v3 credentials, go to ASA2 > Setup > Amazon Creators API and set the Credential Type to “LWA (v3)”
3. If your existing v2 setup works, no action is needed

For questions or issues, visit the help page. Full documentation is available at docs.getasa2.com. A complete list of all changes is in the changelog.