DocumentationTutorialsUse Cases & Blueprints

View schema

Last update: September 11, 2026

CREATED FOR:

  • Developer
  • User

View via the UI

  1. Open your browser and navigate back to the Schema -> Browse section.
  2. Search for the Customer Account schema
  3. Notice that the identities are added to the schema

Schema browse view showing identities added to the schema

View via the API

  1. Select the Step 3 - Get Customer Account Schema and its descriptors API by clicking on it.

    Step 3 - Get Customer Account Schema w/descriptors API request

  2. In the URL of the request replace the <replace me> with the $meta:altId you saved from the previous section (Create Your Schema) to the end of the call like shown below

    Final Step 5 request with altId appended to the URL

  3. Save the edits you’ve made the request

  4. Execute the request by clicking the Send button

You should now see a 200 OK response and you should be able to browse the schema you created through the lens of the XDM JSON structure

Body of the API response showing the schema's XDM JSON structure

Browse further down in the API response to see the identity descriptors you created

Identity descriptors displayed in the API response

Accept headers

Note the Accept header used in the request. This header tells the XDM schema registry to return the schema’s $refs unresolved (i.e. show the bare minimum amount of information) along with its associated descriptors in the API response. Adobe provides other Accept headers you can utilize to get various degrees of detail about the schema.

Accept header field in the Step 3 Get Customer Account Schema request

NOTE
You can read more about the various Accept headers here -> Experience League Schema API Endpoint

To see this in action, change the Accept header to tell the schema registry to respond with all the $ref and allOf fully resolved (i.e. exploded out) and any associated descriptors

  1. Update the Accept header value to the following:
    application/vnd.adobe.xed-full-desc+json; version=1
  2. Save your request using the Save button
  3. Execute your request using the Send button

You should see a response now that looks like this:

Fully exploded schema response showing all resolved properties

NOTE
Notice how all the properties of the schema are now fully displayed in the response whereas in the previous call you only were shown the $ref values of the schema (i.e. what field groups it was referencing) and nothing was fully resolved down to each individual field/property.
NOTE
This is important to understand because when working with APIs you do not always need the fully resolved response if all you are doing is getting the $id of the schema or simply checking its composition
recommendation-more-help
blueprints-learn-help-blueprints