Mitratech · OAuth Scopes

Mitratech OAuth Scopes

OAuth 2.0 searched

Mitratech uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

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.

LegalLegal OperationsEnterprise Legal ManagementMatter ManagementGovernance Risk and ComplianceComplianceWorkflow-AutomationContract Lifecycle ManagementHR ComplianceRisk ManagementImmigrationODataMCP

Scopes: 0 Flows: Method: searched

Scopes (0)

Mitratech implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

📄 Provider scope reference: https://success.mitratech.com/TAP/TAP_Solutions/APIs_and_Integrations/TAP_API_Documentation

Source

OAuth Scopes

generated: '2026-09-13'
method: searched
source: >-
  https://success.mitratech.com/TAP/TAP_Solutions/APIs_and_Integrations/TAP_API_Documentation +
  https://mitratech.com/.well-known/oauth-authorization-server +
  https://mitratech.com/.well-known/oauth-protected-resource
docs: https://success.mitratech.com/TAP/TAP_Solutions/APIs_and_Integrations/TAP_API_Documentation
summary: >-
  Mitratech's OAuth surfaces are scope-bearing but scope-poor. Both published scope vocabularies are a
  single opaque value, and neither is a permission vocabulary — authorization on TAP is carried by the
  TAP user account behind the token, not by the scope.
scopes:
- name: api
  api: Mitratech TAP Workflow Automation API
  description: >-
    The only scope value documented for the TAP token request. Sent as `scope=api` in the
    password-grant body to /auth/identity/connect/token.
  source: https://success.mitratech.com/TAP/TAP_Solutions/APIs_and_Integrations/TAP_API_Documentation
- name: mcp
  api: Mitratech MCP Server
  description: >-
    The only scope in scopes_supported on both the RFC 8414 authorization-server metadata and the
    RFC 9728 protected-resource metadata at mitratech.com.
  source: https://mitratech.com/.well-known/oauth-authorization-server
scope_count: 2
notes:
- >-
  TeamConnect's OAuth documentation describes scope as "(Optional) Specify the scope required for
  access" and publishes no scope values at all. No TeamConnect scopes are recorded here because none
  are published — an honest absence, not an omission.
- >-
  Least privilege is not expressible on TAP. Mitratech's own guidance is to use a Super Admin account
  to obtain the token, warning that a narrower account may silently return incomplete results. An
  agent therefore cannot be granted a read-only or single-object token.

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/mitratech-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.