Request accessTalk to Voyager

Developers

Build on the business record, inside the same authority.

Discuss an integrationPlatform & extensibility

Voyager is a platform, not only a product. APIs, events, webhooks, apps and extensions work on the same records, permissions and approval rules as the people running the business.

The extension model

Records, APIs, events, apps and external systems, inside one boundary.

Everything a developer builds reads and writes Voyager's canonical records. Events describe what changed, apps and extensions add capability, and connected systems exchange data through the same permissions and authority policy as people.

Permissions and authority policy apply on every path
Canonical business recordsOne data modelPeopleOrganizationsWorkSchedulesMoneyFilesRequestsDomain recordsBrowser, desktop and mobile clients use the same governed APIs
APIs
  • Credentials per app and environment
  • Scoped to what the app needs
  • API explorer and testing
Events and webhooks
  • Event catalog
  • Subscriptions with delivery logs
  • Retries and lifecycle controls
Apps and extensionsApp Catalog. Specialist capability on the shared model, no second copy of the data.
External systemsIntegrations act within the scopes each provider grants.
Business NetworkSpecific records and work shared with another organization, by permission.
PartnersDelegated administration across client organizations, each kept separate.
Approval

An API call, app or extension cannot do what the policy would not let a person do. Consequential actions still stop for approval.

Code inherits authority

An app's credential, an event delivery and an action that waits.

Credentials are scoped per app and environment. Events are delivered with logs and retries. Actions through the API meet the same approval policy as the people running the business.

App credential · productionCollections sync
  • Read invoices
  • Read customers
  • Send approved reminders

Issued per app and environment. Governed by the organization's roles and authority policy.

Event · invoice became overdue
  1. Delivery attempt 1503
  2. Retry, delivered200
  3. Delivery log kept2 attempts

Failures show in system health, with retries and lifecycle controls.

API actions from the app
  1. Send reminder, approved templateAllowed
  2. Offer a payment planStopped for approval
  3. Write off the balanceNot permitted

An API call cannot do what the policy would not let a person do.

Illustrative example. Names and scopes are placeholders, not the published API reference.

Building blocks

What developers work with.

APIS AND CREDENTIALS

Read and act on the same records people use.

API credentials are issued per app and environment, scoped to what the app needs, and governed by the organization's roles and authority policies. An API call cannot do what the policy would not let a person do.

EVENTS AND WEBHOOKS

Subscribe to what changes in the business.

An event catalog describes what Voyager emits. Webhook subscriptions deliver those events with delivery logs, retries and lifecycle controls, and failures appear in system health rather than being discovered later.

DEVELOPER PLATFORM

Apps, environments, testing and logs in one place.

The developer platform and SDK cover apps, credentials, environments, an API explorer, events, logs, documentation and testing, so an integration can be built and verified before it touches production data.

EXTENSIONS

Add specialist capability without forking the model.

Extensions and apps add vertical or specialist capability on top of Voyager's canonical records. They use the same data model and authorization, so an extension cannot create a parallel version of your customers or bypass approvals.

Platform model

Extend Voyager without creating a second system.

Every extension point works on Voyager's canonical records. That keeps the business in one context even as partners, apps and custom workflows add to it.

IntegrationsSecurity & trust
App catalog
Discover, install and manage Voyager apps and extensions for your organization.
Partner platform
Agencies, accountants, consultants and implementation partners can run managed services for many client organizations, with each client's data kept separate.
Business Network
Permissioned coordination and shared records between companies, without breaking tenant isolation.
White-label and solution packs
Partners and vertical products can configure branded experiences on the same backend.
Platform Studio
Configure record types, fields, statuses, views, forms, workflows and terminology without code, with preview, versioning and rollback.

Developer answers

What to know before building on Voyager.

Does Voyager have an API?
Yes. Voyager provides APIs, scoped API credentials, webhooks, an event catalog, delivery logs and retries. Browser, desktop and mobile clients use the same governed platform APIs.
Can an app or integration bypass Voyager's approvals?
No. Apps, extensions and API clients act within the permissions granted to their credentials and the organization's authority policy. Consequential actions that need approval still stop for approval.
Can partners build on Voyager for their clients?
Yes. The partner platform supports managed-service providers such as agencies, accountants, consultants and implementation partners, with delegated administration and separate client data.
Where do I start?
Tell us what you want to connect or build, and which Voyager records and events it needs. We will point you to the right credentials, environments and extension model.

Get started

Tell us what you want to build.

Discuss an integrationRequest accessEnterprise deployment

Describe the system, app or partner workflow and the Voyager records it uses. We will help you choose the right interfaces and the authority it should run under.