# Qubitro REST API

The API supports any programming language or framework that can send HTTP requests.

### API Basics

Our API is exposed as an HTTP/1 and HTTP/2 service over SSL. All endpoints live under the URL `https://api.qubitro.com` and then generally follow the REST architecture.

#### Server Specs

The API supports HTTP versions 1, 1.1, and 2, although HTTP/2 is preferred.

TLS versions 1.2 and 1.3 are supported, with resumption.

For more information on TLS support, refer to the [SSL Labs report](https://www.ssllabs.com/ssltest/analyze.html?d=api.qubitro.com\&s=139.178.72.18).

#### Content Type

All requests must be encoded as JSON with the `Content-Type: application/json` header. If not otherwise specified, responses from the Qubitro API, including errors, are encoded exclusively as JSON as well.

### Authentication

All requests to the Qubitro REST API require an API Key passed as a Bearer token in the Authorization header. 

You can generate and manage API Keys in the Qubitro Portal. If needed, configure scopes to limit access to specific projects or actions.

Include the header as follows:

```bash
Authorization: Bearer YOUR_API_KEY
```

#### Creating an API Key

API keys can be created and managed within the Account Credentials section.

{% embed url="<https://qubitro.gitbook.io/qubitro-documentation/platform/credentials/api-keys>" %}
Manage API Keys
{% endembed %}