---
schema_version: "1"
id: 3a535d6a1dbfe1efd588f12799e22aeef73f4eb2f7968ec2049d88331ebd1556
title: January 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_jan_2025.md
canonical_url: https://help.salesforce.com/s/articleView?id=commerce.b2c_com_api_jan_2025.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 432707179952f5649eaf3f205f4f59f4750e2a4fc11da53fece2aaf4594fa0a2
description: SCAPI and SLAS
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# January 2025

SCAPI 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:

- Support added for CORS headers with ports.
- The new `sfdc_correlation_id` response header for the SCAPI Correlation ID is now fully enabled on all instances.
- With B2C Commerce version 25.1:
    - SCAPI/OCAPI Coupons API Update:
        - Retrieved coupons are now sorted by `couponId` if no (optional) sorting order was passed. Previously, the sort order of retrieved coupons wasn't deterministic. For details, see:
            - OCAPI: Get Coupons in [Data Coupons](https://developer.salesforce.com/docs/commerce/b2c-commerce/references/ocapi-data-coupons?meta=Summary)
            - SCAPI: [Coupons Search](https://developer.salesforce.com/docs/commerce/commerce-api/references/coupons?meta=couponsSearch)
        - You can now add multiple remote includes from different sources in the array and create complex and powerful responses. For details, see [Remote Includes](https://developer.salesforce.com/docs/commerce/commerce-api/guide/remote_includes.html).
        - The `x-correlation-id` RESPONSE header is deprecated in some instances and is replaced by the `sfdc_correlation_id` RESPONSE header. For details, see [Match Request and Response Codes with Correlation IDs](https://developer.salesforce.com/docs/commerce/commerce-api/guide/identifying-requests-and-responses.html).

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`. For details, see [Guest Tokens](https://developer.salesforce.com/docs/commerce/commerce-api/guide/slas.html#guest-tokens).