Get Started with the My Trust Center API

Use the Salesforce My Trust Center API to get the events that affect the Salesforce tenants that you’re authorized to access. Events include incidents, maintenance, patch releases, and informational messages. The API returns the same information that you see in My Trust Center, so you can bring it into your own monitoring, alerting, and IT service management tools.

A tenant is a distinct data space that doesn’t implicitly share data with other tenants, such as a Salesforce org, a Marketing Cloud Engagement business unit, or a Commerce Cloud realm. Every response is limited to the tenants that your personal access token (PAT) is authorized to access.

In this guide, you create a PAT, list your tenants, and get a status snapshot across your tenants.

Prerequisites 

  • A Trailblazer account that you can use to log in to My Trust Center. You don’t need a specific My Trust Center role to create a PAT.
  • Access to at least one tenant in My Trust Center.
  • A tool that sends HTTPS requests, such as cURL.

Create a Personal Access Token 

The API authenticates every request with a PAT. Create your first PAT in My Trust Center.

  1. Log in to My Trust Center with your Trailblazer account credentials.
  2. Click the Settings tab.
  3. In the Personal Access Tokens section, click Create Token.
  4. Enter a label of up to 64 characters that identifies where you use the PAT, such as prod-servicenow.
  5. Select an expiry of 7, 15, or 30 days. The default is 30 days.
  6. Copy the PAT and store it in a secure location, such as a secrets manager. My Trust Center shows the PAT only once.

You can have only one active PAT. To create a PAT when you already have one, first revoke your existing PAT in Settings.

Note

Treat your PAT like a password. Anyone who has your PAT can see the events for every tenant that you can access.

Important

To make the examples in this guide easier to run, save your PAT in an environment variable.

Save your PAT
1export MYTRUST_PAT="YOUR_PAT"

List Your Tenants 

All requests go to this base URL.

Base URL
1https://api.salesforce.com/platform/mytrust/v1

To confirm that your PAT works, list the tenants that it’s authorized to access. Send the PAT as a Bearer token in the Authorization header. This example uses pageSize=2 to return two tenants per page.

Request
1curl "https://api.salesforce.com/platform/mytrust/v1/tenants?pageSize=2" \
2  -H "Authorization: Bearer $MYTRUST_PAT"

The response lists your tenants, sorted by tenant ID and cloud. In this example, you have more than two tenants, so the response includes nextPageToken.

Response
1{
2  "tenants": [
3    {
4      "id": "00D000000000001",
5      "cloud": "core",
6      "name": "Example Corporation",
7      "environment": "Production",
8      "myDomain": "example"
9    },
10    {
11      "id": "00D000000000002",
12      "cloud": "core",
13      "name": "Example Sandbox",
14      "environment": "Sandbox",
15      "myDomain": "example--test"
16    }
17  ],
18  "nextPageToken": "opaque-continuation-token"
19}

If the response includes nextPageToken, more tenants are available. To get the next page, send the same request, including pageSize, with the pageToken query parameter set to that value.

Next-page request
1curl "https://api.salesforce.com/platform/mytrust/v1/tenants?pageSize=2&pageToken=$NEXT_PAGE_TOKEN" \
2  -H "Authorization: Bearer $MYTRUST_PAT"

Repeat until the response doesn’t include nextPageToken.

If you get a 401 response, your PAT is missing, invalid, or expired. Check the Authorization header. If the PAT still doesn’t work, revoke it in My Trust Center and create a PAT.

Get a Status Snapshot 

To see what’s happening across your tenants right now, get a status snapshot.

Request
1curl https://api.salesforce.com/platform/mytrust/v1/status \
2  -H "Authorization: Bearer $MYTRUST_PAT"

The response groups events into ongoing and upcoming buckets. Each bucket groups events by event type: patch, incident, maintenance, and informationalMessage. This shortened example shows an ongoing incident.

Response (shortened)
1{
2  "ongoing": {
3    "patch": [],
4    "incident": [
5      {
6        "eventId": "evt-incident-001",
7        "eventType": "incident",
8        "title": "API latency",
9        "description": "Some requests are experiencing elevated latency.",
10        "status": "active",
11        "startTime": "2026-10-08T16:00:00.000Z",
12        "endTime": null,
13        "products": ["Salesforce Services"],
14        "services": ["Core Service"],
15        "scope": {
16          "tenants": {
17            "00D000000000001": {}
18          }
19        }
20      }
21    ],
22    "maintenance": [],
23    "informationalMessage": []
24  },
25  "upcoming": {
26    "patch": [],
27    "incident": [],
28    "maintenance": [],
29    "informationalMessage": []
30  }
31}

Each event’s scope identifies the tenants that the event affects.

A patch release can appear more than once in a snapshot, because each copy represents a separate set of tenants at a separate stage. Don’t de-duplicate the snapshot by eventId.

Note

To get localized response fields, set the locale query parameter to a BCP 47 locale, such as ja-JP. Unsupported values fall back to en-US.

Next Steps