Partner Program Access controls which apps and businesses can use Onyx Partner Platform in production.
Onyx reviews partner access because partner integrations can touch identity, consent, communication, trust assertions, and connectivity flows. Those surfaces must stay clear to users and safe for the account.
Who Can Apply
The partner program is designed for teams building customer-facing products that need approved Onyx capabilities.
Partners can include:
- consumer apps
- fintech apps
- travel products
- membership products
- loyalty programs
- support or service tools
- developer teams building with Onyx ID
Access is not automatic.
Onyx can limit access based on product fit, compliance posture, support readiness, market availability, and current partner capacity.
Review Steps
Partner access can include:
- company review
- app identity review
- use-case review
- requested scope review
- domain verification
- redirect URI review
- webhook review
- connectivity catalogue review where applicable
- support and escalation review
- production approval
Some partners can start in a preview environment before production access is approved.
Preview access does not guarantee production approval.
App Review
Apps must identify themselves clearly before they request user access.
App review can cover:
- app name
- verified domain
- public description
- requested scopes
- consent language
- redirect URIs
- allowed origins
- webhook endpoints
- user-facing support path
Unclear app names, misleading consent copy, excessive scopes, or unsafe redirect settings can block approval.
Production Access
Production access requires a clean launch posture.
Before launch, Onyx can require:
- verified app ownership
- approved scopes
- approved consent copy
- tested sign-in flow
- tested webhook delivery
- working revocation behavior
- support intake readiness
- privacy and security review
- connectivity order testing where applicable
If a capability is not approved, the partner experience should show that it is unavailable.
Gated Capabilities
Some capabilities remain gated even for approved partners.
Gated capabilities can include:
- expanded messaging permissions
- community execution
- support-agent execution
- partner connectivity catalogue access
- market-specific connectivity launches
- advanced event subscriptions
Gated capabilities should return a clear state. Partners should not hide the limitation or retry without a reason.
Access Changes
Partner access can change after approval.
Access can become limited if:
- consent expires
- scopes are revoked
- app review changes
- verification requirements change
- regional availability changes
- abuse or fraud review starts
- webhook security fails
- support requirements are not met
Partners must respect the current access state immediately.