VOCUS enhances user experience by allowing other applications to read and write data via a series of APIs.
| Item | Description |
|---|---|
| Authentication | How to authenticate when making API calls. |
| Directory Concepts | The directory controls identity, access, and basic object structures such as domains and accounts. |
| REST Concepts | General information about working with the REST-based VOCUS APIs. |
| Data Types | |
| Integration Flow | An in-depth example that combines multiple concepts and APIs and provides suggested practices for doing so. |
Most integrations will use multiple APIs to ensure that users can access VOCUS and work with one or more types of data.
Data is shared between all APIs (including application-specific APIs). For example, a user replicated to VOCUS (the "platform") may be used later in a call to FlightRisk as a pilot on a risk assessment.
| URL | Type | Purpose |
|---|---|---|
| VOCUS | ||
| REST | Platform Services: Domain, User, and Tail replication. | |
| SOAP | Legacy Replication Deprecated | |
| FlightRisk | ||
| REST | FlightRisk Services: Risk Assessments, Scheduling, OOOI Times. | |
| SOAP | Legacy Schedule Deprecated | |
| VOCUS SMS | ||
| REST | VOCUS SMS Services | |
API Version 14.1.9203.25249
Copyright ©2008-2025 Polaris Aero, LLC.