Decisiv · OAuth Scopes

Decisiv OAuth Scopes

OAuth 2.0 probed

Decisiv publishes 5 OAuth 2.0 scopes via the authorizationCode and password flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Decisiv API on a user’s behalf.

Tokens are issued from https://login.decisiv.net/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.

Companycommercial-vehicleFleet Managementservice-relationship-managementTelematicsAsset Managementmaintenance-and-repairHeavy Duty TruckingTransportationDealer ManagementJSON:APIWebhook

Scopes: 5 Flows: authorizationCode, password Method: probed

OAuth endpoints

Authorization URL
https://login.decisiv.net/auth/api_gateway

Token URL
https://login.decisiv.net/oauth/token https://portal.decisivapps.com/oauth/token

Flows
authorizationCodepassword

Scopes (5)

Scope	Description	Flows
openid	Request an OpenID Connect ID token alongside the access token.
public	Public / unauthenticated-tier access.
read	Read access to the resources the OAuth Application is provisioned for.
write	Create access to the resources the OAuth Application is provisioned for.
update	Modify access to the resources the OAuth Application is provisioned for.

📄 Provider scope reference: https://api-docs.decisiv.net/docs/api/oauth/

Source

OAuth Scopes

generated: '2026-08-12'
method: probed
source: https://login.decisiv.net/.well-known/openid-configuration
docs: https://api-docs.decisiv.net/docs/api/oauth/
note: >-
  Decisiv's OpenAPI security schemes declare oauth2 flows with EMPTY scope maps in all six specs, so the
  spec-derived pass produced zero scopes. The real scope list comes from the provider's own OAuth 2.0 /
  OIDC discovery document at login.decisiv.net, which publishes scopes_supported. Decisiv does not
  publish a per-resource scope reference page; authorization is granted per OAuth Application through
  account provisioning (a request to an unprovisioned module returns 428 with
  decisiv:access:003 "OAuth Application does not have appropriate provisioning to access this resource"),
  which means the coarse scopes below are the whole published scope vocabulary.
issuer: decisiv.net
authorization_server: https://login.decisiv.net
schemes:
- name: OAuth2AuthorizationCode
  source: openapi/decisiv-account-management-openapi.yml
  status: current
  note: required flow for all new integrations
  flows:
  - flow: authorizationCode
    authorizationUrl: https://login.decisiv.net/auth/api_gateway
    tokenUrl: https://login.decisiv.net/oauth/token
    refreshUrl: https://login.decisiv.net/oauth/token
    scopes_declared_in_spec: 0
- name: OAuth2Password
  source: openapi/decisiv-account-management-openapi.yml
  status: deprecated
  note: >-
    Marked "**Deprecated.**" in the spec description — available only during the migration window to
    the authorization-code flow and slated for removal in a future release.
  flows:
  - flow: password
    tokenUrl: https://login.decisiv.net/oauth/token
    scopes_declared_in_spec: 0
- name: OAuth2Password
  source: openapi/decisiv-global-assets-openapi.yml
  status: deprecated
  flows:
  - flow: password
    tokenUrl: https://portal.decisivapps.com/oauth/token
    scopes_declared_in_spec: 0
scopes:
- scope: openid
  description: Request an OpenID Connect ID token alongside the access token.
  sources: [https://login.decisiv.net/.well-known/openid-configuration]
- scope: public
  description: Public / unauthenticated-tier access.
  sources: [https://login.decisiv.net/.well-known/openid-configuration]
- scope: read
  description: Read access to the resources the OAuth Application is provisioned for.
  sources: [https://login.decisiv.net/.well-known/openid-configuration]
- scope: write
  description: Create access to the resources the OAuth Application is provisioned for.
  sources: [https://login.decisiv.net/.well-known/openid-configuration]
- scope: update
  description: Modify access to the resources the OAuth Application is provisioned for.
  sources: [https://login.decisiv.net/.well-known/openid-configuration]
grant_types_supported:
- authorization_code
- refresh_token
- password
- client_credentials
pkce:
  supported: true
  code_challenge_methods: [S256, plain]
id_token:
  signing_alg: [ES256]
  jwks_uri: https://login.decisiv.net/oauth/discovery/keys
  claims:
  - iss
  - sub
  - aud
  - exp
  - iat
  - username
  - email
  - id
  - first_name
  - last_name
  - name
  - phone
  - roles
  - rbac_groups
  - rbac_permissions
endpoints:
  authorization: https://login.decisiv.net/oauth/authorize
  token: https://login.decisiv.net/oauth/token
  revocation: https://login.decisiv.net/oauth/revoke
  introspection: https://login.decisiv.net/oauth/introspect
  userinfo: https://login.decisiv.net/oauth/userinfo
x-evidence:
- url: https://login.decisiv.net/.well-known/openid-configuration
  http_status: 200
  content_type: application/vnd.api+json
- url: https://login.decisiv.net/.well-known/oauth-authorization-server
  http_status: 200
  content_type: application/vnd.api+json
- url: https://login.decisiv.net/oauth/discovery/keys
  http_status: 200

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