Request a JWT for Experience Edge
Experience Edge for XM provides the following APIs that help you administer your Edge tenant and provide access to your content:
-
Delivery API - GraphQL API that provides access to your published content.
-
Token API - REST API that enables you to manage the API keys used to access the Delivery API.
-
Admin API - REST API that enables you to configure your Edge tenant.
Authorizing your requests
To interact with the Experience Edge APIs, you must authorize your requests depending on the API you want to use.
Request a JWT
-
Create an Edge administration client to obtain a client ID and client secret. You'll use the client ID and client secret when requesting a JWT.
To request a JSON web token (JWT) for Experience Edge, make the following HTTP request using either a JSON or a URL-encoded format:
POST https://auth.sitecorecloud.io/oauth/token
You must provide the following required attributes in the request body:
|
Attribute |
Type |
Description |
Value |
|---|---|---|---|
|
|
|
The group of APIs the JWT is intended for. |
|
|
|
|
The method used to obtain the JWT. |
|
|
|
|
The client ID of your Edge administration client. If you don't know this value, first create an Edge administration client. |
Your client ID. Example: |
|
|
|
The client secret of your Edge administration client. If you don't know this value, first create an Edge administration client. |
Your client secret. Example: |
{
"access_token": "eyJhbG...",
"scope": "...",
"expires_in": 86400,
"token_type": "Bearer"
}In the response:
-
access_tokencontains the JWT. You can use the JWT to:-
Generate an Edge token using the Deploy REST API or the Token API. This lets you authorize your requests to the Delivery API.
-
-
scopecontains the resources the JWT provides access to. The resources depend on the type of credentials you created. -
expires_incontains the validity of the JWT in seconds. Note that JWTs typically expire in 24 hours. After that time, the token is no longer valid and you must request a new token. -
token_typecontains the type of token created, such as Bearer.
Some code examples, images, and UI labels may still use XM Cloud while engineering assets are being updated.