---
schema_version: "1"
id: 84491890275d5e6194a483ee4a404e50bdc165df53a333047cd4d67910b404a9
title: September 2024
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/commerce/264-0-0/b2c_com_api_sept_2024.md
canonical_url: https://help.salesforce.com/s/articleView?id=commerce.b2c_com_api_sept_2024.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: f9b42d80177ddad59a96c379e269fd9b61711bef5e3a104caf44f04bd64b8bb8
description: "SCAPI release, SCAPI fixes, and SLAS Release with the B2C Commerce 24.9.1 release:"
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# September 2024

SCAPI release, SCAPI fixes, and SLAS Release with the B2C Commerce 24.9.1 release:

For more detailed release information, see [B2C Commerce API Release Notes](https://developer.salesforce.com/docs/commerce/commerce-api/references/about-commerce-api/about.html).

SCAPI/OCAPI Release

With B2C Commerce version 24.9.1

- Added a read-only, optional `hashedLogin` field in the response as applicable for the following [Shopper Customers API](https://developer.salesforce.com/docs/commerce/commerce-api/references/shopper-customers?meta=Summary) endpoints:
    - `PATCH /customers/{customerId} (updateCustomer)`
    - `GET /customers/{customerId} (getCustomer)`
    - `POST /customers (registerCustomer)`

SLAS Service Protection

- As part of our bot mitigation strategy for the upcoming holiday season, we are introducing additional service protection:
    - A SLAS service protection mechanism to restrict bad actors or BOTs calling the same SLAS endpoint repeatedly using the same USID (Unique Shopper ID) within a short span of time. This returns a 409 HTTP response. SLAS Trusted System on Behalf (TSOB) logins will have a service protection window of 3 seconds.
- To help you verify the authenticity of callback requests, SLAS provides a SlasCallbackToken (JWT) for each passwordless login and password reset callback that SLAS sends. For more details, see [Verify the SLAS Password Action Callback](https://developer.salesforce.com/docs/commerce/commerce-api/guide/slas.md#verify-the-slas-password-action-callback).
- With B2C Commerce version 24.9.1, added a read-only, optional hashedLogin field in the response as applicable for the following [Shopper Customers API](https://developer.salesforce.com/docs/commerce/commerce-api/references/shopper-customers?meta=Summary) endpoints:
    - `PATCH /customers/{customerId} (updateCustomer)`
    - `GET /customers/{customerId} (getCustomer)`
    - `POST /customers (registerCustomer)`

SLAS:

- To enhance security for the Shopper Login API Access Service (SLAS), a `channel_id` (site) parameter is now required when requesting a guest access token with a `grant_type` of `client_credentials`. This change prevents unauthorized access across different storefronts. Existing customers must update their implementation to include the `channel_id parameter` in the client credential call in guest flows using the schedule in [Guest Tokens](https://developer.salesforce.com/docs/commerce/commerce-api/guide/slas.html#guest-tokens).