Listings API · OAuth Scopes

Listings API OAuth Scopes

OAuth 2.0 probed

Listings API 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.

Business ListingsLocal SEOLocationsReviewsGoogle Business ProfileAnalyticscitation-managementLocal Marketingsocial-publishingMCPagent-native
Scopes: 0 Flows: Method: probed

Scopes (0)

Listings API 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.listingsapi.com/docs/authentication

Source

OAuth Scopes

Raw ↑ 
generated: '2026-09-03'
method: probed
source: https://listingsapi.com/.well-known/oauth-authorization-server, https://listingsapi.com/.well-known/oauth-protected-resource, https://docs.listingsapi.com/docs/authentication, https://github.com/listings-api/listingsapi-mcp (README)
docs: https://docs.listingsapi.com/docs/authentication
oauth:
  applies_to: MCP server (https://listingsapi.com/mcp) only; the REST API authenticates with static API keys.
  issuer: https://listingsapi.com
  authorization_endpoint: https://listingsapi.com/oauth/authorize
  token_endpoint: https://listingsapi.com/oauth/token
  registration_endpoint: https://listingsapi.com/oauth/register
  revocation_endpoint: https://listingsapi.com/oauth/revoke
  grant_types: [authorization_code, refresh_token]
  pkce: S256
  token_endpoint_auth: none
scopes:
  - name: read
    description: >-
      Read access - every lookup and report: locations, listings and citations, reviews,
      posts, analytics. Mirrors the "Read" access level on API keys.
  - name: write
    description: >-
      Write access - create/update locations, reply to reviews, publish posts, connect
      accounts. Mirrors the "Write" access level on API keys.
notes: >-
  scopes_supported [read, write] comes from the provider's own RFC 8414 discovery document.
  API keys carry the same two access levels (Read or Write), chosen at key creation in the
  dashboard; OAuth consent on the MCP server materialises as an API key named after the client.
  A key with Read access covers every lookup; writes need Write access (403 on a write means a
  Read-only key).

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/listings-api-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.