# Introduction

## Unico IDCloud Platform

**IDCloud** is the only identity verification platform that combines security with guaranteed accuracy. With it, you can validate users' identity in a simple and intuitive way using only a selfie, ensuring smoothness and protection in your verification processes.

The platform is versatile and can be adapted for different use cases, allowing you to adjust it according to the needs of your scenario. For this, we offer several [capabilities](https://devcenter.unico.io/unico-idcloud/product-guides/getting-started/capabilities) — features of our platform that meet a wide range of operations and demands. And it is possible to use the IDCloud platform through two integration methods, [by Unico and by Client](https://devcenter.unico.io/unico-idcloud/product-guides/getting-started/by-unico-vs-by-client)**.**

## Integration <a href="#integracao" id="integracao"></a>

The Unico IDCloud platform provides **REST APIs** for identity validation, document capture, signing and other services. You authenticate via OAuth2 (via backend), create verification processes, redirect the user to complete the journey and, finally, query the results.

Our endpoints use **resource-oriented URLs**, predictable and consistent, that **accept and return data in JSON format**, as well as use **standard HTTP status codes** in responses.

{% hint style="warning" %}
**Important Notice about Integrations**

To ensure **stability** and the **security** of our services, it is **mandatory** that integrations with Unico's APIs be carried out **exclusively via backend (server-side)**.

Calls made by the **frontend (browser or client-side)** can be blocked by our systems when we detect multiple IPs or different *user agents* from browsers. In addition, client-side integrations expose authentication keys to risks of **leakage** and **malicious use**, which can result in unauthorized consumption of resources and **additional costs**. **We always recommend: (1)** Implement integrations in the **backend, (2)** Properly use the **headers** and the **authentication** and **(3)** Never expose credentials on the **client-side**.

For more details, consult our full documentation or contact the [**technical support**](https://empresas.unico.io/hc/pt-br/p/atendimentoparaempresas).
{% endhint %}

## Responses <a href="#respostas" id="respostas"></a>

We use conventional response codes to indicate success or failure in a request. In short, codes in the `2xx` range represent success. Codes in the `4xx` range indicate types of validation errors with the provided information or mapped failures. Finally, codes in the `5xx` range indicate a server error or some other unexpected failure.