Skip to content

Commit 53857bc

Browse files
authored
Merge pull request #296 from AdobeDocs/update-endpoint-template
Update data-ingestion-schema-v1.yaml
2 parents 9b98eea + 91258bd commit 53857bc

File tree

16 files changed

+556
-218
lines changed

16 files changed

+556
-218
lines changed

src/_includes/authentication/get-new-bearer-token.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,18 +5,18 @@ curl --request POST \
55
--url 'https://ims-na1.adobelogin.com/ims/token/v3' \
66
--header 'Content-Type: application/x-www-form-urlencoded' \
77
--data 'grant_type=client_credentials' \
8-
--data 'client_id={{client-id-value}}' \
9-
--data 'client_secret={{client-secret-value}}' \
8+
--data 'client_id={{clientId}}' \
9+
--data 'client_secret={{clientSecret}}' \
1010
--data 'scope=openid,AdobeID,profile,email,commerce.aco.ingestion'
1111
```
1212

1313
Replace the following placeholders with your credentials:
1414

15-
- `<client_id>`: The client ID generated for your Adobe developer project
16-
- `<client_secret>`: The client secret generated for your Adobe developer project
15+
- `{{clientId}}`: The client ID generated for your Adobe developer project
16+
- `{{clientSecret}}`: The client secret generated for your Adobe developer project
1717

1818
You can get these credentials from the Adobe Developer Console project details page. If you don't have access to the developer console, contact your system administrator for assistance.
1919

2020
<InlineAlert variant="info" slots="text" />
2121

22-
This token request provisions the required scopes for Adobe Commerce Optimizer data ingestion as listed in the `scope` parameter. For information on managing, refreshing, and revoking bearer tokens, see the [User Authentication Implementation Guide](https://developer.adobe.com/developer-console/docs/guides/authentication/UserAuthentication/) in the *Adobe Developer Console documentation*.
22+
This token request provisions the required scopes for Adobe Commerce Optimizer data ingestion as listed in the `scope` parameter. For information on managing, refreshing, and revoking bearer tokens, see [User Authentication](https://developer.adobe.com/commerce/webapi/rest/authentication/user/) in the *Adobe Commerce REST Guide*.
Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,15 @@
1-
From Cloud Manager, you can find your instance ID in the instance details for your Commerce Optimizer project.
1+
From Cloud Manager, you can find the endpoint URLs and tenant ID (instance ID) in the instance details for your Commerce Optimizer project.
22

33
1. Log in to your [Adobe Experience Cloud](https://experience.adobe.com/) account.
44

55
1. Under **Quick access**, click **Commerce** to open the Commerce Cloud Manager.
66

77
The Commerce Cloud Manager displays a list of instances that are available in your Adobe IMS organization.
88

9-
1. To get the instance ID, click the information icon next to the Adobe Commerce Optimizer instance name.
9+
1. To get the base URLs and instance ID, click the information icon next to the Adobe Commerce Optimizer instance name.
1010

11-
![Access URLs for Commerce Optimizer UI, REST, and GraphQL APIs](../../pages/_images/reporting/aco-instance-details.png)
12-
13-
The instance details page opens, displaying the instance ID and other instance information. The instance ID is displayed in the `Instance ID` field.
14-
15-
You can also find the instance ID from the access URL for the Adobe Commerce Optimizer application interface, the value is in the path, for example `/in:XDevkG9W6UbwgQmPn995r3/`.
11+
![Access URLs for Commerce Optimizer UI, REST, and GraphQL APIs](../../pages/_images/merchandising/aco-instance-details.png)
1612

1713
<InlineAlert variant="info" slots="text" />
1814

19-
If you don't have access to the Commerce Cloud Manager, contact your system administrator.
15+
If you don't have access to Cloud Manager, you can also find the region and tenant ID from the access URL for the Adobe Commerce Optimizer application interface.

src/_includes/authentication/initial-auth-for-api-access.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,12 @@ To get API authentication credentials and tokens, create an Adobe developer proj
22

33
<InlineAlert variant="info" slots="text" />
44

5-
To create Projects for enterprise organizations, you must have a system administrator or developer role with access to the **Adobe Commerce as a Cloud Service – Backend - Commerce Cloud Manager** product. For information on managing developers from the Admin console, see [Managing developers](https://helpx.adobe.com/enterprise/using/manage-developers.html) in the *Adobe Enterprise & Teams Administration Guide*.
5+
Creating projects for enterprise organizations requires a system administrator or developer role with access to the **Adobe Commerce as a Cloud Service – Backend - Commerce Cloud Manager** product. For information on managing developers from the Admin console, see [Managing developers](https://experienceleague.adobe.com/en/docs/commerce/optimizer/user-management) in the *Adobe Commerce Optimizer Guide*.
66

77
1. Log in to the [Adobe Developer Console](https://developer.adobe.com/console).
88

9+
You can also access the Developer Console from the **Get Credentials** section of the [Data Ingestion API Reference](https://developer.adobe.com/commerce/services/reference/rest/). If you use this method, you are automatically directed to the correct organization. You can complete the process to create credentials and generate an access token from there.
10+
911
1. Select the Experience Cloud Organization for the integration.
1012

1113
1. Create an API project.
@@ -22,9 +24,7 @@ To create Projects for enterprise organizations, you must have a system administ
2224

2325
1. Copy the Client ID and the Client Secret values to a secure location.
2426

25-
- Use the Client ID and Client Secret to refresh expired bearer tokens [using curl].
26-
27-
- Include the Client ID in the `x-api-key` header to authenticate API requests.
27+
You use these values to refresh expired bearer tokens.
2828

2929
1. Get the bearer access token.
3030

src/_includes/graphql/endpoints.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,15 +9,15 @@
99

1010
| Environment | Endpoint |
1111
| ------------ | --------:|
12-
| Testing | `https://na1-sandbox.api.commerce.adobe.com/{{tenant-id}}/graphql` |
13-
| Production (Not available yet) | `https://na1.api.commerce.adobe.com/{{tenant-id}}/graphql` |
12+
| Testing | `https://na1-sandbox.api.commerce.adobe.com/{{tenantId}}/graphql` |
13+
| Production (Not available yet) | `https://na1.api.commerce.adobe.com/{{tenantId}}/graphql` |
1414

1515
**URL structure for SaaS endpoints**
1616

1717
```text
18-
https://<region>-<environment-type>.api.commerce.adobe.com/<tenantId>/graphql
18+
https://{{region}}-{{environment-type}}.api.commerce.adobe.com/{{tenantId}}/graphql
1919
```
2020

21-
- `<region>` is the cloud region where your instance is deployed.
22-
- `<environment-type>` is the environment type, such as `sandbox`. If the environment is production, this value is omitted.
23-
- `<tenantId>` is the unique identifier for your organization's specific instance within the Adobe Experience Cloud.
21+
- `{{region}}` is the cloud region where your instance is deployed.
22+
- `{{environment-type}}` is the environment type, such as `sandbox`. If the environment is production, this value is omitted.
23+
- `{{tenantId}}` is the unique identifier for your organization's specific instance within the Adobe Experience Cloud.

src/data/navigation/sections/optimizer.js

Lines changed: 37 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -16,45 +16,49 @@ module.exports = [
1616
title: "Get started",
1717
path: "/optimizer/data-ingestion/using-the-api.md"
1818
},
19-
{
20-
title: "API Reference",
21-
path: "https://developer.adobe.com/commerce/services/reference/rest/",
22-
EventTarget: "_top"
23-
}
24-
]
25-
},
26-
{
27-
title: "Retrieve catalog data",
28-
path: "/optimizer/merchandising-services/",
29-
header: "true",
30-
pages: [
31-
{
32-
title: "Get started",
33-
path: "/optimizer/merchandising-services/using-the-api.md"
34-
},
35-
{
36-
title: "Use cases",
37-
path: "/optimizer/merchandising-services/use-cases.md"
38-
},
39-
{
40-
title: "Limitations",
41-
path: "/optimizer/merchandising-services/limitations.md"
42-
},
43-
{
44-
title: "Monitor and troubleshoot",
45-
path: "/optimizer/merchandising-services/troubleshooting.md"
19+
{
20+
title: "Test API operations",
21+
path: "/optimizer/data-ingestion/api-testing.md"
4622
},
4723
{
4824
title: "API Reference",
49-
path: "https://developer.adobe.com/commerce/services/reference/graphql/",
25+
path: "https://developer.adobe.com/commerce/services/reference/rest/",
5026
EventTarget: "_top"
5127
}
5228
]
5329
},
54-
{
55-
title: "Tutorial",
56-
path: "/optimizer/ccdm-use-case.md"
57-
}
30+
{
31+
title: "Retrieve catalog data",
32+
path: "/optimizer/merchandising-services/",
33+
header: "true",
34+
pages: [
35+
{
36+
title: "Get started",
37+
path: "/optimizer/merchandising-services/using-the-api.md"
38+
},
39+
{
40+
title: "Use cases",
41+
path: "/optimizer/merchandising-services/use-cases.md"
42+
},
43+
{
44+
title: "Limitations",
45+
path: "/optimizer/merchandising-services/limitations.md"
46+
},
47+
{
48+
title: "Monitor and troubleshoot",
49+
path: "/optimizer/merchandising-services/troubleshooting.md"
50+
},
51+
{
52+
title: "API Reference",
53+
path: "https://developer.adobe.com/commerce/services/reference/graphql/",
54+
EventTarget: "_top"
55+
}
56+
]
57+
},
58+
{
59+
title: "Tutorial",
60+
path: "/optimizer/ccdm-use-case.md"
61+
}
5862
]
5963
}
60-
];
64+
]

src/pages/_images/reporting/aco-instance-details.png renamed to src/pages/_images/merchandising/aco-instance-details.png

File renamed without changes.

src/pages/credential/GetCredentialOAuthS2s.js

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ const GetCredentialOAuthS2s = () => {
8181

8282
<GetCredential.Card.DevConsoleLink heading="Developer Console Project" />
8383

84-
<GetCredential.Card.AccessToken helpText="" buttonLabel="Generate and copy token" heading={(<>Access token<br/><br/> <span style="font-weight:normal"><small>Paste the access token into the <strong>Authorization</strong> header in the <strong>Try it</strong> panel below. Then, add the <a href="https://developer.adobe.com/commerce/services/optimizer/data-ingestion/using-the-api/#base-url">instance ID</a> to the <strong>instance ID</strong> field. You only need to do this once; future requests reuse the values automatically.</small></span></>)}/>
84+
<GetCredential.Card.AccessToken helpText="" buttonLabel="Generate and copy token" heading={(<>Access token<br/><br/> <span style="font-weight:normal"><small>Paste the access token into the <strong>Authorization</strong> header in the <strong>Try it</strong> panel below. Then, add the <a href="https://developer.adobe.com/commerce/services/optimizer/data-ingestion/using-the-api/#base-url">instance ID</a> to the <strong>tenantID</strong> field. You only need to do this once; future requests reuse the values automatically.</small></span></>)}/>
8585

8686
<GetCredential.Card.CredentialDetails heading={(<>Credential details<br/><br/> <span style="font-weight:normal"><small>The following Client ID and Organization ID are used to generate the access token:</small></span></>)} orderBy="ClientId,ImsOrgID">
8787
<GetCredential.Card.CredentialDetails.ClientId heading="Client ID (x-api-key)" />
@@ -113,7 +113,7 @@ const GetCredentialOAuthS2s = () => {
113113

114114
<GetCredential.Return.ManageDeveloperConsole label="Manage all your projects and credentials on Adobe Developer Console" direction='/console/projects' />
115115

116-
<GetCredential.Return.AccessToken helpText="" buttonLabel="Generate and copy token" heading={(<>Access token<br/><br/> <span style="font-weight:normal"><small>Paste the access token into the <strong>Authorization</strong> header in the <strong>Try it</strong> panel below. Then, add the <a href="https://developer.adobe.com/commerce/services/optimizer/data-ingestion/using-the-api/#base-url">instance ID</a> to the <strong>instance ID</strong> field. You only need to do this once; future requests reuse the values automatically.</small></span></>)} />
116+
<GetCredential.Return.AccessToken helpText="" buttonLabel="Generate and copy token" heading={(<>Access token<br/><br/> <span style="font-weight:normal"><small>Paste the access token into the <strong>Authorization</strong> header in the <strong>Try it</strong> panel below. Then, add the <a href="https://developer.adobe.com/commerce/services/optimizer/data-ingestion/using-the-api/#base-url">instance ID</a> to the <strong>tenantID</strong> field. You only need to do this once; future requests reuse the values automatically.</small></span></>)} />
117117

118118
<GetCredential.Return.DevConsoleLink heading="Developer Console project" />
119119

src/pages/live-search/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,5 +20,5 @@ The [_Adobe Commerce Event SDK_](../shared-services/storefront-events/sdk/) prov
2020

2121
## Related information
2222

23-
* [Introduction to Live Search](https://experienceleague.adobe.com/docs/commerce-merchant-services/live-search/overview.html?lang=en)
23+
* [Introduction to Live Search](https://experienceleague.adobe.com/en/docs/commerce/live-search/overview)
2424
* [GraphQL queries](https://developer.adobe.com/commerce/webapi/graphql/schema/live-search/)

src/pages/optimizer/admin/using-the-api.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -44,9 +44,9 @@ import GetTenantId from '/src/_includes/authentication/get-tenant-id.md'
4444

4545
Every API request must include a bearer token in the request header:
4646

47-
`Authorization: Bearer {access token}`
47+
`Authorization: Bearer {{accessToken}}`
4848

49-
The bearer token is generated using the credentials from the Adobe developer project for the API integration. The token is valid for 24 hours. When it expires, use the Adobe developer project credentials to [generate a new one](#generate-a-new-access-token).
49+
The bearer token is generated using the credentials from the Adobe developer project for the API integration. The token is valid for 24 hours. When it expires, use the Adobe developer project credentials to generate a new one.
5050

5151
<br></br>
5252

@@ -72,7 +72,7 @@ Include the following headers in GraphQL requests.
7272
| Header Name | Required |Description |
7373
|---------------|----------|------------|
7474
| `Content-Type` | Yes | Specifies the media type of the resource. Accepted value: `application/json`. |
75-
| `Authorization: Bearer {access token}` | Yes | Bearer token generated from IMS credentials. See [Authentication](#authentication). |
75+
| `Authorization: Bearer {{accessToken}}` | Yes | Bearer token generated from IMS credentials.|
7676

7777
## Request template
7878

@@ -82,8 +82,8 @@ Use the following template to submit requests using [curl](https://curl.se/), re
8282
curl --request POST \
8383
--url https://na1-sandbox.api.commerce.adobe.com/{{tenantId}}/admin/graphql \
8484
--header "Content-Type: application/json" \
85-
--header "Authorization: Bearer {access token}" \
86-
--data "{apiPayload}"
85+
--header "Authorization: Bearer {{accessToken}}" \
86+
--data "{{apiPayload}}"
8787
```
8888

8989
For sample requests, see the [tutorial](../ccdm-use-case.md).

0 commit comments

Comments
 (0)