Let us know so we can improve!
The online Trailblazer Community becomes read-only Oct 30, 2026. Read More
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.
The API authenticates every request with a PAT. Create your first PAT in My Trust Center.
prod-servicenow.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.
1export MYTRUST_PAT="YOUR_PAT"All requests go to this base URL.
1https://api.salesforce.com/platform/mytrust/v1To 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.
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.
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.
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.
To see what’s happening across your tenants right now, get a status snapshot.
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.
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.