Custom API Status Report

The Custom API status report enhances transparency and reduces troubleshooting time by providing real-time visibility into the registration status of your Custom APIs. When you activate a code version that includes Custom APIs, the registration process can yield different outcomes for each endpoint. Previously, developers had to manually sift through logs to diagnose issues, but the Custom API status report simplifies this by offering clear, actionable feedback.

You can also use the B2C Commerce CLI to verify if your custom endpoints are correctly registered and reachable. First, see B2C CLI, MCP and Tooling SDK to install the tool and authenticate.

Once configured, use the CLI to verify your custom endpoints:

1# Check the status and availability of custom API endpoints
2b2c scapi custom status

For a complete list of custom endpoint CLI commands, see Custom APIs.

Note

Key Benefits

Real-time status reporting: Get immediate feedback on endpoint registration status.
Error transparency: Understand why an endpoint failed to register.
Reduced debugging time: No manual log searching.
Improved development workflow: Quickly identify and resolve endpoint issues.

Endpoint Registration Status

Every Custom API endpoint can have one of the following registration statuses:

Status	Description	Accessible?
`active`	Endpoint was successfully registered and is ready to handle requests.	Y
`not_registered`	Endpoint failed to register due to an error in configuration or implementation.	N

Use the Custom API Status Report

Authentication

The Custom API status report requires authentication using the Account Manager OAuth 2.0 flow with the required scope:

sfcc.custom-apis (read-only)

Endpoint URL

1GET https://{shortCode}.api.commercecloud.salesforce.com/dx/custom-apis/v1/organizations/{organizationId}/endpoints

Parameters

Parameter	Type	Required	Description
`shortCode`	Path	Yes	An eight-character string assigned to a realm for routing purposes, for example: `kv7kzm78`
`organizationId`	Path	Yes	A short string that identifies your B2C Commerce instance, for example: `f_ecom_zzte_053`
`status`	Query	No	Filter endpoints by status: `active` or `not_registered`

Response Format

The endpoint returns a JSON object containing:

activeCodeVersion: The currently active code version
total: Total number of endpoints discovered across all sites and cartridges
limit: Number of endpoints included in this response. This count matches the filter criteria and equals total when no filters are applied.
data: Array of endpoint objects with detailed information
filter: Object containing applied filters. This is present only if filters are used in the request.

Each endpoint object includes:

Field	Description
`id`	Unique identifier for the endpoint (consistent across code version activations)
`apiName`	Name of the API, for example: `loyalty-info`
`apiVersion`	Version of the API, for example: `v1`
`cartridgeName`	Name of the cartridge containing the endpoint
`endpointPath`	The endpoint path, for example: `/customers`
`httpMethod`	HTTP method, for example: `GET`, `POST`)
`operationId`	Operation identifier from the OpenAPI schema
`implementationScript`	Name of the implementation script file
`schemaFile`	Name of the OpenAPI schema file
`siteId`	Site identifier where the endpoint is registered
`securityScheme`	Security scheme used by the endpoint
`status`	Registration status (`active` or `not_registered`)
`errorReason`	Error description (only present when status is `not_registered`)

Examples

List All Endpoints

Get information for all Custom API endpoints in your organization:

1curl -X GET \
2  'https://{shortCode}.api.commercecloud.salesforce.com/dx/custom-apis/v1/organizations/{organizationId}/endpoints' \
3  -H 'Authorization: Bearer {access_token}'

Response:

1{
2  "activeCodeVersion": "version1",
3  "limit": 3,
4  "data": [
5    {
6      "id": "10bd7f2dc40ab7aede7f0d60e5c3a783",
7      "apiName": "loyalty-info",
8      "apiVersion": "v1",
9      "cartridgeName": "my_custom_cartridge",
10      "endpointPath": "/customers",
11      "httpMethod": "GET",
12      "implementationScript": "customers.js",
13      "operationId": "getLoyaltyInfo",
14      "securityScheme": "ShopperToken",
15      "schemaFile": "loyalty-schema.yaml",
16      "siteId": "Sites-MyStore-Site",
17      "status": "active"
18    },
19    {
20      "id": "fd2e726fc9e23dac4951bfe325146c24",
21      "apiName": "loyalty-info",
22      "apiVersion": "v1",
23      "cartridgeName": "my_custom_cartridge",
24      "endpointPath": "/rewards",
25      "httpMethod": "POST",
26      "implementationScript": "rewards.js",
27      "operationId": "addReward",
28      "securityScheme": "AmOAuth2",
29      "schemaFile": "loyalty-schema.yaml",
30      "siteId": "Sites-MyStore-Site",
31      "status": "active"
32    },
33    {
34      "id": "7f8cfdf0534476b858d080b9059bc07e",
35      "apiName": "loyalty-info",
36      "apiVersion": null,
37      "cartridgeName": "my_custom_cartridge",
38      "endpointPath": null,
39      "errorReason": "Schema file ../broken-schema.yaml in API folder loyalty-info must not be a relative path.",
40      "httpMethod": null,
41      "implementationScript": "broken-endpoint.js",
42      "operationId": "brokenOperation",
43      "securityScheme": null,
44      "schemaFile": "../broken-schema.yaml",
45      "siteId": "Sites-Site",
46      "status": "not_registered"
47    }
48  ],
49  "total": 3
50}

Filter by Status

Get endpoints that failed to register:

1curl -X GET \
2  'https://{shortCode}.api.commercecloud.salesforce.com/dx/custom-apis/v1/organizations/{organizationId}/endpoints?status=not_registered' \
3  -H 'Authorization: Bearer {access_token}'