Overview

This documentation describes the available options for integrating Kape Services into your ecosystem.

Currently, two integration approaches are supported:

  1. Kape Client API SDK

  2. Kape API Interface

Kape Client API SDK

The Kape Client API SDK is the recommended way to integrate with Kape Services. It provides a high-level wrapper around the Kape API interfaces and manages essential tasks such as authorization, authentication, and caching.

The SDK is implemented in Rust and ships with language bindings, header files, and frameworks for the following programming languages:

  • Swift

  • Kotlin

  • Go

  • C#

  • C/C++

  • Rust

The SDK does not provide VPN connection functionality.

Instead, it supports the following features:

  • Authorization & authentication management (token handling)

  • Server location, instance, and protocol configuration management

  • SmartLocations

  • Speed testing

  • Client-side protocol pecking

  • Identity protection

  • eSIM support

  • Subscription & in-app purchase handling

Kape API Interface

For developers working with programming languages not supported by the SDK, direct integration with the Kape API is also possible.

While the SDK automatically handles business-critical aspects such as authentication, caching, and error handling, developers integrating directly with the API must implement these responsibilities themselves.

⚠️ Important Considerations

  • Implement proper authentication flows

  • Manage caching on the client side

  • Respect and handle API rate limits

Direct API integration provides maximum flexibility but should only be chosen when the SDK cannot be used.

Next Steps

NextWhite-Label Integration

Last updated