# Introduction

The Suble Cloud rest API operates using the HTTPS protocol and utilizes JSON for its data format. This means all requests either submitting data or requesting data is expected to use the JSON format.

### Authorization

For authorization it uses the **Bearer Authentication** standard to implement JWT and a custom implementation for API tokens. For more information, see below

{% tabs %}
{% tab title="Project Key (Token)" %}
Project keys are generated and linked to a project, this means the key is locked to only work inside the project and cannot generate more project keys or new projects on the user's behalf.\
\
To authorize requests to Suble Cloud API, add "apikey" as prefix to the autorization header.\
Example:

`apikey xxxx-xxxx-xxxx`
{% endtab %}

{% tab title="User Token (JWT)" %}
User tokens are generated when a user logins to the Stacket Group Platform, they are used by the dashboard to communicate with our rest api. The user token can therefore be used for billing, creating project and everything a project key can do.

{% hint style="warning" %}
All requests are logged, therefore the user token will be authenticating on your behalf.
{% endhint %}
{% endtab %}
{% endtabs %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.suble.io/master.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.