SingleFile · OAuth Scopes

SingleFile OAuth Scopes

OAuth 2.0 derived

SingleFile publishes 2 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the SingleFile API on a user’s behalf.

Tokens are issued from https://api.demo.singlefile.ai/o/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.

CompanyComplianceLegalEntity ManagementCorporate ComplianceRegistered AgentBusiness FilingsRegulatoryAPIWebhooksOAuth
Scopes: 2 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://api.demo.singlefile.ai/o/token/
Flows
clientCredentials

Scopes (2)

ScopeDescriptionFlows
read Read access to entities, organizations, orders, documents, jurisdictions and tasks clientCredentials
write Create and update entities, organizations, orders, documents and jurisdictions clientCredentials

Source

OAuth Scopes

Raw ↑
generated: '2026-07-21'
method: derived
source: openapi/singlefile-openapi.yml
schemes:
- name: OAuth2ClientCredentials
  source: openapi/singlefile-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.demo.singlefile.ai/o/token/
  description: 'OAuth 2.0 Client Credentials flow. Exchange client_id/client_secret at the token
    endpoint for a 1-hour bearer token; send it as Authorization: Bearer <token>.'
scopes:
- scope: read
  description: Read access to entities, organizations, orders, documents, jurisdictions and
    tasks
  flows:
  - clientCredentials
  sources:
  - openapi/singlefile-openapi.yml
- scope: write
  description: Create and update entities, organizations, orders, documents and jurisdictions
  flows:
  - clientCredentials
  sources:
  - openapi/singlefile-openapi.yml