> For the complete documentation index, see [llms.txt](https://docs.connect.jfrog.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.connect.jfrog.io/developers/api-reference/connect-api-reference/overview.md).

# API Reference v1 (Legacy)

Each device can send up to three API calls in a minute. If you reach the limit, you will receive an appropriate response code. Please check the response codes and send no more calls than the limit. Otherwise, your device may get banned for API calls.\
\
All calls require a `user_token` and some of them require a `device_token`. 

Token retrievals might have slight differences between agent versions. We strongly recommend upgrading the Agent to the latest version available.

### Data Format

* Endpoint payload data is in JSON format.
* Input parameters in Connect, such as project name, group, device, access tokens, etc., are case sensitive.

## User Token

The `user_token` can be found in the Settings category on Connect dashboard under your account. 

## Device Token

{% hint style="success" %}
**Connect Agent Compatibility**: The Connect Agent versions 7.0 and higher do not support Connect API v1. If your devices have Connect Agent 7.0 or higher and you want to use the API, use Connect API v2.
{% endhint %}

Devices with agent **5.4** and above, run the agent with the flag `--print-token` to receive the device token: `/etc/connect/service/ConnectAgent --print-token`

Here's a ready-to-use script to grab the device token:

{% tabs %}
{% tab title="Python" %}

```python
import subprocess

CONNECT_AGENT_PATH = "/etc/connect/service/ConnectAgent"
AGENT_FLAG_TO_GET_DEVICE_TOKEN = "--print-token"
 
user_token = "Your user token can be found in the Connect UI"
device_token = subprocess.check_output(CONNECT_AGENT_PATH + ” ” + AGENT_FLAG_TO_GET_DEVICE_TOKEN, shell=True)
```

{% endtab %}

{% tab title="Bash" %}

```
#! /bin/bash
/etc/connect/service/ConnectAgent --print-token
```

{% endtab %}
{% endtabs %}

Devices with agent **5.3** and below, `device_token` can be found in the file `/etc/connect/service/settings.json` 


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.connect.jfrog.io/developers/api-reference/connect-api-reference/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.