> For the complete documentation index, see [llms.txt](https://t1t.gitbook.io/t1c-js-guide-v3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://t1t.gitbook.io/t1c-js-guide-v3/v3.1.4/status-codes.md).

# Status codes

## HTTP Status Codes

T1C uses the following HTTP response codes when handling a request.

In case of an error the response will contain a body with more detailed information about the error:

```javascript
{
  description: "some error description",
  code: "some error code"
}
```

All possible values of the codes are described below in "Application Status Codes"\
The description field contains more information

## Application Status Codes

{% hint style="warning" %}
These errors are still in draft. These can change until the final release of the v3
{% endhint %}

### General Trust1Connector errors

| Code | Description                           |
| ---- | ------------------------------------- |
| 100  | general t1c error                     |
| 101  | Module not supported                  |
| 102  | Module not available                  |
| 103  | Module not implemented                |
| 104  | function not supported                |
| 105  | function not available                |
| 106  | function not implemented              |
| 107  | service not supported                 |
| 108  | service not available                 |
| 109  | service not implemented               |
| 110  | Pace layer error                      |
| 111  | Reader error                          |
| 112  | Notification error                    |
| 160  | Digest error                          |
| 115  | Initialisation error                  |
| 116  | DistributionService error             |
| 117  | Rest exception                        |
| 118  | JSON Parsing error                    |
| 119  | JWT parsing error                     |
| 120  | Forbidden error                       |
| 121  | Unauthorized error                    |
| 122  | Invalid DS JWE                        |
| 123  | Device keystore missing               |
| 125  | Parameter exception                   |
| 130  | Proxy service exception               |
| 131  | Invalid T1C state exception           |
| 199  | T1C unavailable exception (JS)        |
| 500  | Agent consent missing or expired (JS) |

### Transaction errors

| Code | Description               |
| ---- | ------------------------- |
| 300  | General transaction error |
| 301  | Pin error                 |
| 304  | Puk error                 |
| 305  | Not supported error       |

### Certificate errors

| Code | Description               |
| ---- | ------------------------- |
| 400  | General certificate error |

### File (exchange) errors

| Code | Description                            |
| ---- | -------------------------------------- |
| 800  | General fileexchange error             |
| 801  | IO exception (files/folder)            |
| 803  | Access exception ( not enough rights ) |
| 804  | Type related errors                    |
| 805  | Entity related errors                  |
| 806  | configuration related error            |

#### Error codes coming from v2

| Old code | New code       | example description                                                              |
| -------- | -------------- | -------------------------------------------------------------------------------- |
| 351      | 803            | /Library/Updates/ProductMetadata2.plist (Operation not permitted)                |
| 352      | 803            | /Library/Updates/ProductMetadata2.plist (Operation not permitted)                |
| 353      | 803            | /Library/Updates/ProductMetadata2.plist (Operation not permitted)                |
| 354      | 801            | Source '/Users/gilles/Desktop/fileextest/test.plist' does not exist              |
| 355      | 112            | No valid dir path returned, no valid file path returned, Timeout, No PIN entered |
| 356      | 804            | No Type with name test was found in entity with name testEnt,                    |
| 357      | 804            | type with name testType already exists                                           |
| 358      | not applicable | error 801 will be thrown with a more detailed message                            |
| 359      | not applicable |                                                                                  |
| 360      | 805            | Entity with name testEnt already exists                                          |
| 361      | 805            | No Entity with name testEnt was found                                            |
| /        | 806            | No configuration found (file-exchange config file is missing/deleted…)           |

### Internal errors

| Code | Description    |
| ---- | -------------- |
| 900  | Internal error |


---

# 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 dynamically by asking a question.

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

```
GET https://t1t.gitbook.io/t1c-js-guide-v3/v3.1.4/status-codes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.