# Prerequisites

## Trust1Connector API DNS

The  Trust1Connector API v3 exposes a secure REST API on the client device. Trust1Team has created a `t1c.t1t.io` DNS entry (or customer-specific DNS entry) that points to `127.0.0.1` in order to facilitate SSL communication. This means that if the customer infrastructure uses a proxy for all network traffic, an exemption **must** be made for `t1c.t1t.io` to always point to the origin device's loopback address. 

If no exemption is made and `https://t1c.t1t.io` is handled by a proxy, it will redirect to `127.0.0.1` IP of the proxy server instead of the local machine, and the Trust1Connector API will be unreachable.

## Distribution Service

In order to correctly function, the Trust1Connector API **must** be able to connect to its configured Distribution Service. You must allow REST traffic to the following URLs (if applicable):

* Acceptance: `https://acc-ds.t1t.io`
* Production: `https://ds.t1t.io`

## Disk Space

The T1C-Proxy (necessary for shared environments only) requires ± 250Mb of space

The T1C-API is installed in user space and also requires ± 250Mb of space **for every user**. 

## API Key

All endpoints of the Trust1Connector API are secured and require a JWT to access. To obtain a token, an [API key **must** be exchanged](/t1c-js-guide-v3/v3.3.0-1/core/authenticated-client.md#retrieving-a-jwt-token). This API key must be requested from Trust1Team, or created by the customer if they are hosting their own Distribution Service

## Operating System

Right now Trust1Conector support two operating systems;

* MacOS 10.9 or higher
* Windows 8.1 or higher

### Windows 8.1 or higher

To run in user-space on Windows 8.1 or higher some components have to be set on the operating system

#### Registry keys

Below you can find a list of all registry keys that will be created for the working of the Trust1Connector, All these keys are added to HKCU

HKEY\_CURRENT\_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

![](/files/-MMv9c3wya04bC3Y5v6y)

HKEY\_CURRENT\_USER\SOFTWARE\Trust1Team\Trust1Connector

![](/files/-MS3-X-S73JspFgln6iM)

## Cookies

When running in a shared environment a cookie is used to store the user's consent, the following cookie  will be used:

```
t1c-agent-proxy
```

�


---

# 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://t1t.gitbook.io/t1c-js-guide-v3/v3.3.0-1/prerequisites.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.