BALAD CORP · OAuth Scopes

BALAD CORP OAuth Scopes

OAuth 2.0 searched

BALAD CORP uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

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.

CompanyPaymentsRemittancesCross-Border PaymentsFintechEgyptPayoutsMoney TransferBankingAPI
Scopes: 0 Flows: Method: searched

Scopes (0)

BALAD CORP implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

Source

OAuth Scopes

Raw ↑
generated: '2026-07-18'
method: searched
source: https://developers.balad.tech/authorization-1459814m0.md
docs: https://developers.balad.tech/authorization-1459814m0.md
schemes:
  - name: OAuth2ClientCredentials
    flow: clientCredentials
    tokenUrl: /identity/v1/token
    source: openapi/balad-corp-gateway-openapi.yml
# Balad documents that access tokens are "scoped to specific APIs" and returns a `scope`
# claim on the token response, but does NOT publish an enumerated scope/permission reference.
# The product-area scope groups below are the granularity Balad names in its docs; individual
# scope string values are not published and are therefore NOT invented here.
scope_groups:
  - name: remittances
    description: Balad Link money-transfer / payout APIs (create, cancel, status, reconciliation).
  - name: collections
    description: Collection / invoice APIs (referenced in docs; not enabled for all partners).
  - name: bills
    description: Bill payment APIs (billers, providers, bill payments).
  - name: vouchers
    description: Voucher APIs (referenced in docs).
scopes: []
notes: Enumerated scope values are not published by Balad; only product-area scoping is documented.