TrustArc · OAuth Scopes

TrustArc OAuth Scopes

OAuth 2.0 searched

TrustArc publishes 1 OAuth 2.0 scope via the implicit flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the TrustArc API on a user’s behalf.

Tokens are issued from https://login.truste.com/oauth/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

PrivacyData PrivacySCIMIdentityAuthenticationOpenID ConnectUser ProvisioningPrivacy ManagementConsent ManagementCookie ConsentPreference ManagementData Subject RightsDSRPrivacy GovernanceData MappingPrivacy AssessmentsPIADPIAGDPRCCPACPRAData Privacy FrameworkTRUSTeAI GovernanceResponsible AIComplianceCertificationsRegTechTrust CenterEnterprise Saas

Scopes: 1 Flows: implicit Method: searched

OAuth endpoints

Authorization URL
https://login.truste.com/oauth/authorize

Token URL
https://login.truste.com/oauth/token

Flows
implicit

Scopes (1)

Scope	Description	Flows
openid	OpenID	implicit

📄 Provider scope reference: https://trustarchelp.zendesk.com/hc/en-us/articles/49881862843155-Authorization-and-Authentication

Source

OAuth Scopes

generated: '2026-08-27'
method: searched
source: openapi/_original/trustarc-guardian-openapi.json
docs: https://trustarchelp.zendesk.com/hc/en-us/articles/49881862843155-Authorization-and-Authentication
discovery: well-known/trustarc-openid-configuration.json
note: >-
  TrustArc's OAuth surface is effectively scope-free. The published discovery document
  declares scopes_supported: ["openid"] and nothing else, and the Guardian OpenAPI declares
  the same single scope. The token response echoes "openid profile email", but profile and
  email are not advertised as grantable scopes in discovery. Authorization is decided by
  ROLE (SUPER_ADMIN / ADMIN / DESIGNER), not by scope — see
  authentication/trustarc-authentication.yml. No scopes or permissions reference page exists
  in the TrustArc help center; the search returned none. Nothing invented to fill the gap.
schemes:
  - name: guardianAuth
    source: openapi/_original/trustarc-guardian-openapi.json
    flows:
      - flow: implicit
        authorizationUrl: https://login.truste.com/oauth/authorize
        tokenUrl: https://login.truste.com/oauth/token
scopes:
  - scope: openid
    description: OpenID
    flows: [implicit]
    sources:
      - openapi/_original/trustarc-guardian-openapi.json
      - well-known/trustarc-openid-configuration.json
observed_in_token_response:
  - openid
  - profile
  - email

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/trustarc-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.