Choosing an SDK
Help deciding whether to use a client- or server-side SDK.
A Software Development Kit (SDK) is a collection of software tools that we maintain in a specific language.
Using an SDK is the easiest way to interact with our API. You can install an SDK using your project's package manager and use the objects and methods it provides to interact with our API at a high level.
We offer two types of SDKs:
|Client-side SDKs||Server-side SDKs|
|Location||Browsers or mobile devices||Corporate networks or web servers|
|Function||Feature parity (although, slight differences may exist)|
|Security||Can be inspected by end user||Cannot be inspected by end user|
|Secret keys||No, never!||Yes|
The biggest difference between client- and server-side SDKs is security. Because you cannot use secret keys in a client-side SDK, you will not be able to use riskier API features.
Client-side SDKs typically run on customers' own devices. They can be compromised by users who unpack a mobile app to examine the SDK bytecode or use their browser's developer tools to inspect internal site data. As a result, you should never use a secret API key in a client-side or mobile application.
Server-side SDKs, on the other hand, operate within server-architected applications running on your own infrastructure or trusted cloud-based infrastructure. Neither of these locations is directly accessible by end users. Because of the limited access to server-based applications, our secret API keys can safely retrieve snippets without needing to obscure or filter out sensitive data.
We offer SDKs for a growing number of languages and technologies. Some, but not all, languages have client- and server-side SDKs available.
Explore the following SDK reference guides for specific details about how to use Jahuty with your tech stack:
|SDK Reference||Side||Public API Keys?||Secret API keys?|
If you don't see your language above, you can use our API directly.