{"title":"Getting Started with DX Portal and APIs","html":"

This guide provides an overview of how to access, authenticate, and consume APIs through the DXM
platform.

Overview

The DXM platform provides a centralized interface for working with APIs across Digital Realty
services. The DX Portal serves as the primary entry point to:

All API requests are executed through the DXM Gateway, which enforces authentication and
authorization.

Step 1: Explore APIs in DX Portal

The API section in the DX Portal provides access to all available APIs. It enables:

Each API specification includes details about required credentials and supported environments.

Testing APIs via Swagger UI

Each API can be tested directly from the portal using the built-in Swagger UI, without any
external tooling.

The presence of an Authorize button in Swagger UI indicates whether the API requires
authentication:

Client Credentials Tab (API-Level)

Each API in the portal includes a Client Credentials tab at the API level. This tab contains a
helper note that specifies exactly which credentials are required for that particular API and
environment.

Always check the Client Credentials tab before authenticating. The required credential set
varies by API and environment.

The note lists which credentials are available for that specific API, for example:

API is available on the following environments:Global SSO QAGlobal SSO Production

Client Secret and Client ID are available in Settings -> Client Credentials.

This tells you which credential sets are available for the API. Use the credentials associated
with the environment you are accessing. Since DXM uses a 1:1 environment mapping, credentials
are only valid for their corresponding environment. Using credentials from a different environment
will result in authentication failures.

Step 2: Retrieve Client Credentials

Client credentials are available in DX Portal -> Settings.

These include:

These credentials are required to obtain access tokens.

Security considerations

Client Secrets must be handled securely. They must not be exposed in client-side code, logs, or
version control systems.

Step 3: Obtain an Access Token

Most APIs require an access token for authentication. The correct token endpoint to use is
determined by the Client Credentials tab of the specific API. The same note that lists
available environments also tells you which credential type is in use:

If required credentials or access are not available, they can be requested via the Contact Us
form.

Access Token Flow

Authentication follows a client credentials flow:

  1. Check the API's Client Credentials tab to identify the correct token endpoint.
  2. Submit your Client ID and Client Secret to that endpoint.
  3. Receive an access token (JWT).
  4. Use the token in API requests.

Step 4: Execute API Requests

APIs can be consumed in several ways. Use whichever best fits your workflow. All protected API
requests must include the access token in the Authorization header:

Authorization: Bearer <access_token>\n

Swagger UI (in DX Portal)

This is the quickest way to explore and test without leaving the portal.

Swagger UI automatically uses the server URL associated with the environment you are accessing.
No additional server selection or environment configuration is required.

cURL

Suitable for quick command-line testing or scripting:

curl -X GET \"https://gateway.digitalrealty.com/accounts/v1/example\" \\\n  -H \"Authorization: Bearer <access_token>\" \\\n  -H \"Content-Type: application/json\"\n

API Clients (Postman, Insomnia, etc.)

Any HTTP client can be used. Configure the Authorization header with
Bearer <access_token> and use the base URL corresponding to your target environment.

Programmatic / SDK Usage

APIs can be called from any language or framework.

","publishedAt":"2026-09-03T17:10:11.000+00:00","updatedAt":"2026-09-25T09:50:46.000+00:00","audience":"external"}