Skip to main content

Brilliance One Technology

API-first integration. Practical provider choice.

Connect Brilliance One to selected third-party services, automated workflows, custom applications, communications, payments, and supported external systems.

Business & government focused•API first•Built to evolve
Integrations at Brilliance One

Integration strategy

One platform, connected workflows.

The API identifies the authorized tenant and user context, while supported third-party connections use their own provider configuration and permissions.

API first

Developer API

Authenticated API endpoints support integrations, external applications, portals, and automation. API access is included for users; individual permissions still apply.

Connected services

Communications & operations

Supported providers may connect email, SMS, scheduling, web meetings, notifications, payments, and operational processes.

Flexible

Bring your own provider

Where implemented, connect approved vendor accounts and credentials; third-party fees and supported scopes vary.

Provider examples

Connect the systems your organization needs.

Examples from the current product direction include MailerSend, Google and Microsoft calendars, SmarterMail, Zoom, Google Meet, Microsoft Teams, payment processors, and configurable AI providers. Availability varies by feature and deployment.

  • OpenAPI-based integration patterns and developer documentation
  • API-key and authenticated session/JWT access as required by endpoint
  • Tenant- and record-level authorization checks
  • Provider credential security and rate limits
  • Audit and event visibility appropriate to workflow
  • No guarantee that every listed provider is live in every edition

Next Step

Let's discuss your requirements.

Capabilities, deployment options, contractual requirements, and roadmap items should be confirmed for your specific use case.