Where is your SDK?

📘

What is an SDK?

A software development kit (SDK) is a collection of software development tools in one installable package. SDKs are designed to give developers the resources they need to build applications for a certain software platform or programming language. They typically include libraries, documentation, sample code, and other resources that make it easier to develop software for a particular platform or technology.

An SDK can also include APIs (Application Programming Interfaces), which are a set of tools and protocols for building software and applications. SDKs can also include a debugger, a compiler and other development tools which can help in the development process. SDKs are commonly used for mobile development, gaming, and other specific platforms.

Overall, an SDK is designed to provide developers with the necessary tools to create software for a specific platform or technology, helping to streamline the development process and make it easier for developers to create high-quality software.

API First

Given the nature of SDKs, and the fact they usually are constrained to a single or specific set of programming languages, Preczn has chosen an API First approach.

This means, you can easily code to our API in the language native to your platform. Preczn is designed to integrate to your platform with as little bloat as possible. You can leverage Preczn with just a pair of API Keys and simple calls.

Here are just a few reasons Preczn utilizes an API First approach:

• Flexibility: When you use an API directly, you have more flexibility in terms of what you can do with the data or functionality that the API provides. You're not limited to the functionality that the SDK provides.

• Smaller Footprint: SDKs can be large and include a lot of unnecessary components, which can slow down your application. Using an API directly allows you to only include the code that you actually need, making your application leaner and faster.

• Maintenance: SDKs can be difficult to maintain over time because the underlying APIs they are built on top of can change or be deprecated. Using an API directly allows you to respond to changes more quickly and easily.

• Support: SDKs can be tied to a specific programming language or framework. This can cause problems if you want to switch to a different language or framework, as the SDK may not be available for that platform. Using an API directly allows you to work in any language or framework that can make HTTP requests.

But, where is your SDK?

If you still prefer integrating to Preczn via SDK, Preczn is built using the OpenAPI (formerly Swagger) specification, and you can easily generate an SDK using your preference of over 40 programming languages. You can find our Open API JSON here.