---
schema_version: "1"
id: 3dc9bba387c9ad8d70cb956899c3e0c5ac1b78e46a18e2a85cc71150cf7ca001
title: Use the SCAPI Admin APIs
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/commerce-cloud/commerce-api/guides/use-admin-api.md
canonical_url: https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/use-admin-api.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: b05cbabefdb9b02d5bc29337c76b682869d26d6da40a4518c8ab7bca7da5217b
products:
  - Composable Storefront
  - Salesforce APIs
---
# Use the SCAPI Admin APIs

This section contains guidance and information for specific APIs in the SCAPI Admin API family.

## Admin API Overview

The SCAPI Admin APIs enable backend operations, integrations, and automation for your B2C Commerce implementation. All Admin APIs require Account Manager authentication.

For the full, current list of Admin APIs and endpoint details, use the [B2C Commerce API references](https://developer.salesforce.com/docs/commerce/commerce-api/references).

## Authentication Prerequisites

Before using SCAPI Admin APIs, ensure you have:

1. **Account Manager credentials** - Set up through Account Manager in Business Manager
2. **Appropriate permissions** - Admin APIs require specific role-based permissions
3. **API client configuration** - Some Admin APIs require dedicated API client setup
4. **Base URL and organization ID** - Obtain from your Business Manager instance

For authentication setup details, see [Authorization](https://developer.salesforce.com/docs/commerce/commerce-api/guide/authorization.html).

## Common Automation Scenarios

These scenarios are implementation patterns you can adapt. API capabilities and surfaces evolve over time, so always validate endpoint details against the [B2C Commerce API references](https://developer.salesforce.com/docs/commerce/commerce-api/references).

### Scenario 1: Automated Inventory Synchronization
**Goal:** Sync inventory levels from an external warehouse management system (WMS) to B2C Commerce

**Implementation:**
1. **Extract:** Retrieve inventory data from your WMS
2. **Transform:** Map WMS data to OCI inventory record format
3. **Load:** Use **Admin Inventory API** to bulk update availability
4. **Monitor:** Track sync status and handle errors

**Key APIs:** Admin Inventory

### Scenario 2: CDN Configuration Management
**Goal:** Automate CDN zone configuration across multiple environments

**Implementation:**
1. **Define:** Create CDN zone configuration templates
2. **Deploy:** Use **Admin CDN API** to create and configure zones
3. **Configure:** Set up WAF rules, SSL certificates, and cache policies
4. **Monitor:** Enable log forwarding for CDN analytics

**Key APIs:** Admin CDN

### Scenario 3: Product Catalog Updates
**Goal:** Automate daily product data synchronization from a Product Information Management (PIM) system

**Implementation:**
1. **Extract:** Get product updates from PIM system
2. **Validate:** Verify product data format and required fields
3. **Update:** Use **Admin Product API** to update product attributes, prices, and availability
4. **Verify:** Confirm updates through **Shopper Product API**

**Key APIs:** Admin Product, Admin Pricing, Admin Inventory

### Scenario 4: Customer Data Integration
**Goal:** Sync customer profiles between B2C Commerce and a Customer Data Platform (CDP)

**Implementation:**
1. **Identify changes:** Detect customer profile updates in either system
2. **Sync:** Use **Admin Customer API** for bulk updates or individual profile changes
3. **Reconcile:** Handle conflicts and maintain data consistency
4. **Audit:** Log all sync operations for compliance

**Key APIs:** Admin Customer

### Scenario 5: Multi-Site Configuration Deployment
**Goal:** Deploy consistent site settings across multiple B2C Commerce sites

**Implementation:**
1. **Define:** Create configuration templates for site preferences
2. **Deploy:** Use **Admin Site API** to apply settings across sites
3. **Validate:** Verify configurations through API calls
4. **Document:** Track configuration changes for audit purposes

**Key APIs:** Admin Site, Admin Configuration

## Additional Resources

- For ongoing API additions and changes, monitor the [Commerce API release notes](https://developer.salesforce.com/docs/commerce/commerce-api/references/about-commerce-api/about.html).
- For Storefront Next operational context, see [Managed Runtime in Storefront Next](https://developer.salesforce.com/docs/commerce/sfnext/guide/sfnext-mrt-section.html).
- [CDN zones:](https://developer.salesforce.com/docs/commerce/commerce-api/guide/cdn-zones.html) Configure content delivery settings, including web application firewall (WAF) rules, and log forwarding, and also configure certificates.
- [Omnichannel Inventory (OCI):](https://developer.salesforce.com/docs/commerce/commerce-api/guide/inventory-impex-best-practices.html) Manage product inventory for products.
- The Shopper Login Admin API information is categorized as part of the Shopper APIs. For details, see [SLAS Admin.](https://developer.salesforce.com/docs/commerce/commerce-api/references/auth-admin?meta=Summary)

## Next Steps

Use the following links to optimize your storefront's performance and security:

- [Test and Measure Your APIs](https://developer.salesforce.com/docs/commerce/commerce-api/guide/performance.html#test-and-measure-your-apis)
- [Security](https://developer.salesforce.com/docs/commerce/commerce-api/guide/security.html)