Fulfil OAuth Scopes
Fulfil publishes 2 OAuth 2.0 scopes via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Fulfil API on a user’s behalf.
Tokens are issued from https://{merchant_id}.fulfil.io/oauth/token.
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.
OAuth endpoints
https://{merchant_id}.fulfil.io/oauth/authorize
https://{merchant_id}.fulfil.io/oauth/token
authorizationCode
Scopes (2)
| Scope | Description | Flows |
|---|---|---|
| user_session | Grants an API session acting on behalf of the authorizing user; shown as the granted scope in the OAuth token response example in Fulfil's official OAuth guide and used in the official Python client's OAuth session example. | |
| sale.channel:read | Read access to the sale.channel model; used in Fulfil's official headless offline-access example, illustrating the model:permission scope pattern Fulfil uses for granting access to individual ERP models. |
📄 Provider scope reference: https://developers.fulfil.io/rest_api/oauth/
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.
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/scopes/fulfil-io-scopes"
curl "https://apis.io/api/v1/scopes?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.