Beyond Pricing · OAuth Scopes

Beyond Pricing OAuth Scopes

OAuth 2.0 searched

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

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

CompanyShort-Term RentalsVacation RentalsRevenue ManagementDynamic PricingHospitalityProperty ManagementTravelPricingJSON:API
Scopes: 9 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://developers.beyondpricing.com/o/token/
Flows
clientCredentials

Scopes (9)

ScopeDescriptionFlows
accounts:read Read account information clientCredentials
compsets:read Read competitive set data clientCredentials
insights:read Read market insights clientCredentials
listings:read Read listings clientCredentials
listings:write Modify listings clientCredentials
neyoba:ask Ask Neyoba clientCredentials
reservations:read Read reservations clientCredentials
user:read Read user information clientCredentials
user:write Create and modify users clientCredentials

Source

OAuth Scopes

Raw ↑
generated: '2026-07-18'
method: searched
source: openapi/beyond-pricing-openapi-original.yml
docs: https://developers.beyondpricing.com/getting-started/authentication/
authorization_server_metadata: https://developers.beyondpricing.com/.well-known/oauth-authorization-server
notes: >-
  Scopes must first be enabled for the OAuth application, then token-tier rules
  apply. App-level scope (user:write) may only be used on an application-level
  token (no user_id); user-level scopes (listings:read, listings:write,
  reservations:read, accounts:read, insights:read) require a user-scoped token
  when the app has require_user_scoped_tokens enabled. PATs (bpat_...) reuse the
  same scope names at runtime even though OpenAPI cannot encode scopes for the
  non-oauth bearer scheme.
scope_tiers:
  app_level:
  - user:write
  user_level:
  - listings:read
  - listings:write
  - reservations:read
  - accounts:read
  - insights:read
  cross_tier:
  - user:read
schemes:
- name: oauth2
  source: openapi/beyond-pricing-openapi-original.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://developers.beyondpricing.com/o/token/
  description: Use OAuth2 client credentials to mint an application token, or add `user_id`
    and optional `credential_id` in the Authorize dialog to request a user- or credential-scoped
    token.
scopes:
- scope: accounts:read
  description: Read account information
  flows:
  - clientCredentials
  sources:
  - openapi/beyond-pricing-openapi-original.yml
- scope: compsets:read
  description: Read competitive set data
  flows:
  - clientCredentials
  sources:
  - openapi/beyond-pricing-openapi-original.yml
- scope: insights:read
  description: Read market insights
  flows:
  - clientCredentials
  sources:
  - openapi/beyond-pricing-openapi-original.yml
- scope: listings:read
  description: Read listings
  flows:
  - clientCredentials
  sources:
  - openapi/beyond-pricing-openapi-original.yml
- scope: listings:write
  description: Modify listings
  flows:
  - clientCredentials
  sources:
  - openapi/beyond-pricing-openapi-original.yml
- scope: neyoba:ask
  description: Ask Neyoba
  flows:
  - clientCredentials
  sources:
  - openapi/beyond-pricing-openapi-original.yml
- scope: reservations:read
  description: Read reservations
  flows:
  - clientCredentials
  sources:
  - openapi/beyond-pricing-openapi-original.yml
- scope: user:read
  description: Read user information
  flows:
  - clientCredentials
  sources:
  - openapi/beyond-pricing-openapi-original.yml
- scope: user:write
  description: Create and modify users
  flows:
  - clientCredentials
  sources:
  - openapi/beyond-pricing-openapi-original.yml