Quickstart

Make your first API call!

Before you get started with this section, pleasure ensure you have the following 3 pieces of data with you:

  1. Your App ID

  2. Your App's RSA private key

  3. The Org ID corresponding to your testing/live environment

For (1) and (2), revisit the Authentication section.

For (3), revisit the Testing Environment section.

Introduction

The Unifize APIs are crafted following RESTful standards, ensuring that interaction with resources is consistent and intuitive. The APIs are endpoint-driven and typically represent distinct resources, allowing for clear, organized, and efficient communication between systems.

All interactions are managed through the JSON data format, which necessitates setting the content type to application/json. This requirement is enforced for both request and response bodies unless otherwise specified, facilitating seamless data exchange and integration with various applications. Such consistent data handling simplifies interaction and enhances compatibility with different platforms and programming environments.

Authentication and Authorization

Authentication is a necessary aspect of utilizing the Unifize APIs and is implemented via app tokens. These tokens are generated according to the guidelines detailed in the App Tokens page.

Additionally, authorization is handled via a permissions framework, which grants granular control over access levels and operations. Permissions can be set initially during app creation and remain flexible, allowing for modifications as the needs of the application evolve. This dual-layered security model ensures that the Unifize APIs provide robust protection for sensitive operations and data.

Organizations

Central to Unifize's architecture are logical entities known as "Organizations," which help partition and manage resources within the system. The Org Id of these organizations must be specified during the initial token request process. This token, once embedded within a JWT, eliminates the need for repeatedly specifying the Org Id in further API calls, streamlining authentication processes and reducing complexity.

You can read more about Organizations in the Concepts and Terminologies page.

Test it out

To do this using your preferred programming language, the only requirements are:

  • A library to mint JWTs

  • A library to read/parse PEM files

  • A library to make network requests

Below are some examples in commonly used programming languages.

Also see the API Reference.

Prerequisites:

Last updated