Motadata · OAuth Scopes

Motadata OAuth Scopes

OAuth 2.0 searched

Motadata 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.

AIOpsMonitoringObservabilityITSMService DeskNetwork MonitoringLog ManagementIT OperationsApplication Performance MonitoringOpenTelemetry

Scopes: 0 Flows: Method: searched

Scopes (0)

Motadata 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://docs.motadata.com/serviceops-docs/integration-docs/managing-request-using-api

Source

OAuth Scopes

specification: API Commons OAuth Scopes
specificationVersion: '0.1'
provider: Motadata
providerId: motadata
generated: '2026-08-29'
method: searched
source: https://docs.motadata.com/serviceops-docs/integration-docs/managing-request-using-api
docs: https://docs.motadata.com/serviceops-docs/integration-docs/managing-request-using-api
description: >-
  Motadata ServiceOps issues OAuth 2.0 access tokens through a password grant at
  /api/oauth/token. The token response carries a `scope` field, but Motadata documents exactly
  one value and publishes no scopes/permissions reference page. Authorization is enforced by the
  ServiceOps user the token is minted for — the role and permission set of that account — rather
  than by scope. There is no consent screen and no scope selection step.
api: motadata:serviceops
flows:
  - flow: password
    tokenUrl: https://{serviceops-host}/api/oauth/token
    client_auth: 'Basic base64(ClientID:ClientSecret)'
scopes:
  - name: other-api-scope
    description: >-
      The only scope value Motadata documents in the token response. It is not described as
      partitioning access to any subset of the API; it appears to be a constant.
    source: https://docs.motadata.com/serviceops-docs/integration-docs/managing-request-using-api
scope_count: 1
notes:
  - >-
    ObserveOps (the other Motadata product) has no OAuth surface at all — it authenticates with a
    Personal Access Token, a static cookie, or a username/password session, and authorizes by
    user permissions. See authentication/motadata-authentication.yml.
  - >-
    No scopes were invented to fill this file. One documented scope is the honest count.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com

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