SCAPI release, SCAPI fixes, and SLAS Release with the B2C Commerce 24.9 release:
For more detailed release information, see B2C Commerce API Release Notes.
SCAPI/OCAPI Release
- Added support for Cross-Origin Resource Sharing (CORS). For details, see CORS in SCAPI and the CORS API.
- For the Shopper Products getProduct and getCategory endpoints and the Campaigns getCampaign endpoint, you can now set a time window, called the Validity Period. The validity period is used for server-side cache expiration to prevent serving stale content. For additional details, see “Cache Expiration for Objects with a Validity Period” in Server-Side Web-Tier Caching.
- Added response timeout handling for all instance types. For details, see Error Response Codes.
- Set cache expiration for objects with a Validity Period for the Shopper Products getProduct and getCategory endpoints and the Campaigns getCampaign endpoint. For details, see Cache Expiration for Objects with a Validity Period.
- For SCAPI / OCAPI calls using a SLAS JWT, added the
Disable the Modification of the Issuer Datetoggle to invalidate a customer JWT after a password change. When the toggle is set, a 401InvalidAccessTokenExceptionresponse code is returned when trying to use an existing request token after a password change. When the toggle is not set, the error response is only thrown if the time between the token issuer date and the password modification date exceeds 30 seconds.