Rillet · OAuth Scopes

Rillet OAuth Scopes

OAuth 2.0 searched

Rillet 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 Rillet API on a user’s behalf.

Tokens are issued from https://api.rillet.com/oauth2/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.

CompanyFintechERPAccountingFinanceGeneral LedgerAccounts ReceivableAccounts PayableInvoicingSaaS

Scopes: 2 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://api.rillet.com/oauth2/authorize

Token URL
https://api.rillet.com/oauth2/token

Flows
authorizationCode

Scopes (2)

Scope	Description	Flows
read	Read access to Rillet resources (list/retrieve operations).	authorizationCode
write	Write access to Rillet resources (create/update/delete operations).	authorizationCode

📄 Provider scope reference: https://docs.api.rillet.com/docs/mcp

Source

OAuth Scopes

generated: '2026-07-21'
method: searched
source: well-known/rillet-oauth-protected-resource.json
docs: https://docs.api.rillet.com/docs/mcp
schemes:
- name: oauth2
  source: well-known/rillet-oauth-authorization-server.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://api.rillet.com/oauth2/authorize
    tokenUrl: https://api.rillet.com/oauth2/token
    pkce: S256
scopes:
- scope: read
  description: Read access to Rillet resources (list/retrieve operations).
  flows: [authorizationCode]
  sources: [well-known/rillet-oauth-protected-resource.json]
- scope: write
  description: Write access to Rillet resources (create/update/delete operations).
  flows: [authorizationCode]
  sources: [well-known/rillet-oauth-protected-resource.json]
notes: >-
  Coarse-grained read/write scopes advertised in RFC 9728 protected-resource
  metadata. Effective authorization is further constrained by the connected
  user's role within Rillet (Owner / Admin / Accountant / view-only). Direct
  API-key (Bearer) access is not scope-limited at the token level.