---
schema_version: "1"
id: 772cf532ed93a56ce1e69edc5601e6cb110800e5785ebf52e7cb6532f2caea0c
title: February 2025
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/commerce/264-0-0/b2c_com_api_feb_2025.md
canonical_url: https://help.salesforce.com/s/articleView?id=commerce.b2c_com_api_feb_2025.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: bc7ed39ac3493400d76e733b1d2256530632ed67257aebda3df8fba3a8cfd5da
description: SCAPI, OCAPI, and SLAS
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# February 2025

SCAPI, OCAPI, and SLAS

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:

- Runtime version update for internal SCAPI supporting applications. No customer impact is anticipated.
- - API request path validation now identifies empty path segments and handles them consistently across various components.
    - Support added for CORS headers with ports.
    - Update to the 01/07/2025 correlation ID header announcement: The new `sfdc_correlation_id` response header for the SCAPI Correlation ID is now fully enabled for SCAPI on all instances:
        - On sandbox and development instances, the deprecated `x-correlation-id` response header is no longer returned.
        - On staging and production instances, the deprecated `x-correlation-id` response header is still available, but is subject to removal in a future release.
    - Security updates. No customer impact is anticipated.
    - With B2C Commerce version 25.2:
        - The [Shopper Search](https://developer.salesforce.com/docs/commerce/commerce-api/references/shopper-search?meta=Summary) and [Shopper Products](https://developer.salesforce.com/docs/commerce/commerce-api/references/shopper-products?meta=Summary) APIs now support Page Meta Tag Rules. You can create Page Meta Tags in Business Manager (Merchant Tools > SEO > Page Meta Tag Rules) using a rule-based approach to enhance storefront pages with unique meta tag content and increase the SEO value across Product List Pages (PLPs) and Product Detail Pages (PDPs). A new optional `page_meta_tags` expansion, which controls the inclusion of page meta tags rules, has been added to `/product-search` and `/products`.

OCAPI:

- With B2C Commerce version 25.2:
    - Fixed an issue with the [createScapiRemoteInclude()](https://salesforcecommercecloud.github.io/b2c-dev-doc/docs/current/scriptapi/html/index.html?target=class_dw_system_RemoteInclude.html) script functionality when used in combination with a Shopper API. As an example, this led to a 500 exception during the use of the Shopper Baskets API.

SLAS:

- [SLAS 4xx Logs](https://developer.salesforce.com/docs/commerce/commerce-api/guide/slas.html#view-slas-error-logs-in-log-center) are now available in Log Center. Log information includes the `correlationID`, which you can use for end-to-end request tracking.
- SLAS now supports custom query parameters for the [/login](https://developer.salesforce.com/docs/commerce/commerce-api/references/shopper-login?meta=authenticateCustomer) endpoint.
- SLAS now supports merging claims for [Azure IDP](https://developer.salesforce.com/docs/commerce/commerce-api/guide/slas-identity-providers.html#supported-identity-providers).
- The SLAS [PasswordReset](https://developer.salesforce.com/docs/commerce/commerce-api/guide/slas-password-reset.html#slas-password-reset-flow) flow no longer requires PKCE. You can now make password reset requests using the new, optional `hint` query parameter instead of a Proof Key for Code Exchange (PKCE) `code_challenge` and `code_verifier`. For details, see [Password Reset](https://developer.salesforce.com/docs/commerce/commerce-api/guide/slas-password-reset.html).
- Improved error handling and validation to return more meaningful error messages for [Auth0 IDP](https://developer.salesforce.com/docs/commerce/commerce-api/guide/slas-identity-providers.html#supported-identity-providers).
- The `channel_id` (site) parameter is now required when requesting a guest access token with a `grant_type` of `client_credentials`. This change enhances security by preventing 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. For details, see [Guest Tokens](https://developer.salesforce.com/docs/commerce/commerce-api/guide/slas.html#guest-tokens).
    - The original schedule was 09/01/2024 for all sandbox tenants and 10/01/2024 for all other non-production tenants. We will now implement this change for all non-production tenants starting 02/10/2025.
- As of 02/10/25, we are now strictly enforcing the [documented rate limit](https://developer.salesforce.com/docs/commerce/commerce-api/guide/slas.html#slas-rate-limits) of 25 requests per minute (RPM) for the [/jwks endpoint](https://developer.salesforce.com/docs/commerce/commerce-api/references/shopper-login?meta=getJwksUri).
- In preparation for the removal of the SLAS\_ORGANIZATION\_ADMIN (Account Manager API-Client) and SLAS\_TRUSTED\_AGENT\_READ\_ONLY (Account Manager User) Account Manager roles, these roles were removed from the SLAS code base. Because these roles were never made available for SLAS production use, no customer impact is anticipated.
- Additional performance improvements included.