Create an OAuth Server-to-Server credential
The credential gives you the Client ID, Client Secret and Organization ID you enter below. You need developer access to the Adobe Commerce as a Cloud Service - Backend - Commerce Cloud Manager product in your organization.
Open your project
Sign in to the Adobe Developer Console and select the organization that owns your Commerce instance.
- Open an existing project or create a new one.
Add the Commerce API
In your workspace, open Add service and select API.
- Select Adobe Commerce as a Cloud Service and click Next.
- On the Configure API page, select OAuth Server-to-Server and click Save configured API.
Copy the credential values
Open the OAuth Server-to-Server credential of the workspace.
- Copy the Client ID, the Client Secret and the Organization ID (it ends in
@AdobeOrg). - Note the Technical account email. You add it to Commerce in the next section.
- Check that the credential’s scopes include
commerce.accs.
Give the technical account Commerce permissions
REST calls run as the credential’s technical account, so it must be an Admin user of the Commerce environment you connect, with a role that grants the resources you need. Each environment (for example production and staging) needs its own credential and its own Admin user.
Assign a role
In the Commerce Admin, add the technical account email as an Admin user and assign it a role.
- Roles are managed in System > Permissions > User Roles.
- Under Role Resources, choose All or select the resources listed below. Actions that use a resource the role does not include return 401 Unauthorized.
Find your REST endpoint
Open Adobe Experience Cloud, go to the Commerce Cloud Service instances page, and click the information icon next to your instance. Copy the REST endpoint, for example https://na1.api.commerce.adobe.com/AbCYab34cdEfGHiJ27123. Do not add /rest or /V1.
Choose a Store Code (optional)
Cloud Service selects the store scope with a Store header instead of the URL. StackOne sends the Store Code you enter as that header.
- Leave it empty to send no
Storeheader. defaulttargets the default store view, andallruns requests in the global scope.- Or enter a specific store view code, as listed by the List Store Views action.
Link the Account
Connect
- Click Connect.
- If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider’s authorization flow.
- Once authorization is successful, you will see a confirmation popup.
Use Actions