Akia · OAuth Scopes

Akia OAuth Scopes

OAuth 2.0 searched

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

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

CompanyHospitalityHotelsVacation RentalsGuest ExperienceMessagingArtificial IntelligenceAgentsProperty ManagementCheck-In

Scopes: 16 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://sys.akia.com/oauth/authorize https://sys.akia.ai/oauth/authorize

Token URL
https://api.akia.com/oauth/token https://sys.akia.ai/oauth/token

Flows
authorizationCode

Scopes (16)

Scope	Description	Flows
audiences:write	Developer will be create and manage audiences on user's account.
customers:read	Developer will be able to see information about user's customers.
customers:write	Developer will be able to see create and modify user's customers.
messages:read	Developer will be able to see messages sent and received to user's customers.
messages:write	Developer will be able to send messages to user's customers.
mini_apps:partner_products	Developer will be able to provide products guests can purchase through mini apps.
mini_apps:read	Developer will be able to read data and resources from user's mini apps.
mini_apps:write	Developer will be able to create and update user's mini apps.
offices:read	Developer will be able to see information about user's office.
offices:write	Developer will be able to modify and delete information about user's office.
properties:read	Developer will be able to see information about user's property.
properties:write	Developer will be able to modify and delete information about user's property.
reports:read	Developer will be able to read data and metadata of reports.
tasks:read	Developer will be able to read tasks and task queues on user's account.
users:read	Developer will be able to see staff and departments of user's property.
users:write	Developer will be able to create, modify, and delete staff and departments.

📄 Provider scope reference: https://api.akia.com/docs/scopes

Source

OAuth Scopes

generated: '2026-08-06'
method: searched
source: https://api.akia.com/docs/scopes
docs: https://api.akia.com/docs/scopes
schemes:
- name: OAuth2
  type: oauth2
  source: https://api.akia.com/docs/authentication
  flows:
  - flow: authorizationCode
    authorizationUrl: https://sys.akia.com/oauth/authorize
    tokenUrl: https://api.akia.com/oauth/token
    refreshUrl: https://api.akia.com/oauth/token
  - flow: authorizationCode
    authorizationUrl: https://sys.akia.ai/oauth/authorize
    tokenUrl: https://sys.akia.ai/oauth/token
    source: well-known/akia-oauth-authorization-server.json
    note: 'The RFC 8414 authorization-server metadata advertises sys.akia.ai as the
      issuer for the MCP resource; the developer docs describe sys.akia.com for the
      REST API dialog. Both are recorded as observed.'
scope_delimiter: ','
scopes:
- scope: audiences:write
  label: Audiences
  description: Developer will be create and manage audiences on user's account.
- scope: customers:read
  label: Customers (Read)
  description: Developer will be able to see information about user's customers.
- scope: customers:write
  label: Customers
  description: Developer will be able to see create and modify user's customers.
- scope: messages:read
  label: Messages (Read)
  description: Developer will be able to see messages sent and received to user's
    customers.
- scope: messages:write
  label: Messages
  description: Developer will be able to send messages to user's customers.
- scope: mini_apps:partner_products
  label: Partner Products
  description: Developer will be able to provide products guests can purchase through
    mini apps.
- scope: mini_apps:read
  label: Apps (Read)
  description: Developer will be able to read data and resources from user's mini
    apps.
- scope: mini_apps:write
  label: Apps
  description: Developer will be able to create and update user's mini apps.
- scope: offices:read
  label: Offices (Read)
  description: Developer will be able to see information about user's office.
- scope: offices:write
  label: Offices
  description: Developer will be able to modify and delete information about user's
    office.
- scope: properties:read
  label: Properties (Read)
  description: Developer will be able to see information about user's property.
- scope: properties:write
  label: Properties
  description: Developer will be able to modify and delete information about user's
    property.
- scope: reports:read
  label: Reports
  description: Developer will be able to read data and metadata of reports.
- scope: tasks:read
  label: Tasks (Read)
  description: Developer will be able to read tasks and task queues on user's account.
- scope: users:read
  label: Users (Read)
  description: Developer will be able to see staff and departments of user's property.
- scope: users:write
  label: Users
  description: Developer will be able to create, modify, and delete staff and
    departments.
mcp_resource_scopes:
  resource: https://sys.akia.ai/mcp
  scopes_supported:
  - customers:read
  - messages:read
  source: well-known/akia-oauth-protected-resource.json
x-evidence:
  fetched: '2026-08-06'
  url: https://api.akia.com/docs/scopes
  http_status: 200
  content_type: text/html; charset=utf-8
  note: 'The scope table is server-rendered HTML on Akia''s own developer docs; the
    16 scopes above are transcribed verbatim from it. No OpenAPI declares them.'