Edicom · OAuth Scopes

Edicom OAuth Scopes

OAuth 2.0 none

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

CompanyEDIE-InvoicingTax ComplianceB2B IntegrationiPaaSVAT ReportingPEPPOL
Scopes: 0 Flows: Method: none

Scopes (0)

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

No OAuth scopes documentation found. Edicom iPaaS page mentions OAuth2/OIDC support but no public API documentation with scopes was found.

📄 Provider scope reference:

Source

OAuth Scopes

edicom-scopes.yml Raw ↑ 
generated: '2026-10-18'
method: none
source: ''
scopes: []
note: 'No OAuth scopes documentation found. Edicom iPaaS page mentions OAuth2/OIDC support but no public API documentation with scopes was found.'

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