connect-sdk, connect-adapter, connect-provider-sdk, and connect-cruises) still get new releases. The other packages, including cloud-sdk, data-sdk, and storefront-sdk, are frozen at their final release. They remain installable under their original licenses. New integrations should treat the documented HTTP APIs, schemas, authentication model, and webhooks as the supported contract.
The SDKs
Cloud SDK
@voyant-travel/cloud-sdk for vault, messaging, browser, video, realtime, and search.Connect SDK
@voyant-travel/connect-sdk for the operator and connection control plane and the normalized data plane.Data SDK
@voyant-travel/data-sdk for geography, aviation, FX, SEO, and business data.Connect family
connect-adapter, connect-provider-sdk, and connect-cruises for building on Connect.Shared design
All three primary clients follow the same pattern:- A factory function, for example
createVoyantCloudClient,createVoyantConnectClient, orcreateVoyantDataClient, plus an equivalent class constructor. - An
apiKeyoption, and transport options such asbaseUrl,headers, and a customfetch. - Methods grouped into namespaces by domain.
- A shared internal transport (
@voyant-sdk/sdk-core) so behavior is consistent. That package is private; you only ever import the public SDK.
One token, scoped per action
Every SDK authenticates with a Voyant API token. The same token works across products; what it can do is determined by its scopes. See Authentication for how tokens and scopes work, and the per-service pages for the exact scope each method needs.Consistent transport and errors
The SDKs JSON-encode request bodies, skip null and undefined query params, parse JSON responses, and unwrap{ data } envelopes by default. Failures throw a single VoyantApiError carrying status, requestId, and body. See Errors and transport.
Installing
cloud-sdk and data-sdk, these commands install the final npm release. Confirm that the installed client covers the endpoints your integration needs, and use the documented HTTP API when it does not.