My Oracle Support Banner

Differences in Available Properties Using SCIM Filter Between Admin and Storefront (Doc ID 2647088.1)

Last updated on DECEMBER 01, 2023

Applies to:

Oracle Commerce Cloud Service - Version 21.1.1 to 21.1.1 [Release 21A]
Information in this document applies to any platform.


You may notice differences in the payload responses, as well as the available properties you can filter on between similar/same endpoints that are available on both Admin and Storefront rest API.

For the most part this is intended, as these are two different applications and the data made available to each will be different as well. You need to approach each instance you encounter such differences as a separate issue that needs to be discussed. Some of these differences are obviously intended, and documented.



A good example would be the /products endpoint, and specifically the available properties you can filter using SCIM with that endpoint. Notice, the is simply not available at the storefront endpoint, but is available at the same corresponding endpoint in admin. This is not a bug, but there are changes we can make to the application in some circumstances to adjust this behavior (See below)


Admin API: co "TEST"

        - This will return the expected results, the products that match the given you are sending

Storefront API: co "TEST"

        - This will result in an error, because this field ( is not available to filter on using SCIM on this endpoint.

        - {errorCode: "85003", message: "Invalid attribute in query:", status: "400"}






To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.