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.
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
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.