Archer Daniels Midland · OAuth Scopes

Archer Daniels Midland OAuth Scopes

OAuth 2.0 probed

Archer Daniels Midland 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.

AgricultureFood ProcessingCommoditiesSupply ChainFortune 100Nutrition
Scopes: 0 Flows: Method: probed

Scopes (0)

Archer Daniels Midland 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.

These scopes are not read from an ADM API product — ADM publishes no developer portal and no API reference. They are read verbatim from the OpenID Connect discovery document ADM's own www.adm.com host serves (HTTP 200, application/json, 2026-09-04). The issuer is https://www.adm.com/ and the endpoints sit under /api/episerver/connect/, i.e. this is the Optimizely (Episerver) CMS authorization server that fronts adm.com itself. Recorded because it is a real, first-party, machine-readable authorization surface on the company's domain; NOT because ADM sells API access under these scopes. The three OpenAPI documents in openapi/ are API-Evangelist-authored (x-generated-from: documentation) and declare an apiKey scheme, not OAuth, so nothing here was derived from them.

Source

OAuth Scopes

Raw ↑
generated: '2026-09-04'
method: probed
source: https://www.adm.com/.well-known/openid-configuration
docs: null
note: >-
  These scopes are not read from an ADM API product — ADM publishes no developer portal and no API
  reference. They are read verbatim from the OpenID Connect discovery document ADM's own
  www.adm.com host serves (HTTP 200, application/json, 2026-09-04). The issuer is
  https://www.adm.com/ and the endpoints sit under /api/episerver/connect/, i.e. this is the
  Optimizely (Episerver) CMS authorization server that fronts adm.com itself. Recorded because it
  is a real, first-party, machine-readable authorization surface on the company's domain; NOT
  because ADM sells API access under these scopes. The three OpenAPI documents in openapi/ are
  API-Evangelist-authored (x-generated-from: documentation) and declare an apiKey scheme, not
  OAuth, so nothing here was derived from them.
provider_metadata:
  issuer: https://www.adm.com/
  authorization_endpoint: https://www.adm.com/api/episerver/connect/authorize
  token_endpoint: https://www.adm.com/api/episerver/connect/token
  userinfo_endpoint: https://www.adm.com/api/episerver/connect/userinfo
  end_session_endpoint: https://www.adm.com/api/episerver/connect/logout
  jwks_uri: https://www.adm.com/.well-known/jwks
  grant_types_supported:
  - authorization_code
  - refresh_token
  - client_credentials
  code_challenge_methods_supported:
  - S256
  token_endpoint_auth_methods_supported:
  - client_secret_basic
  - client_secret_post
scope_count: 5
scopes:
- name: openid
  description: OpenID Connect — request an ID token for the authenticated subject.
  source: scopes_supported in the published discovery document
- name: offline_access
  description: Issue a refresh token so the client can renew access without the user present.
  source: scopes_supported in the published discovery document
- name: profile
  description: Access the subject's profile claims.
  source: scopes_supported in the published discovery document
- name: email
  description: Access the subject's email claim.
  source: scopes_supported in the published discovery document
- name: roles
  description: Access the subject's role claim, used by the CMS for content authorization.
  source: scopes_supported in the published discovery document

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/archer-daniels-midland-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.

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