# Public Server Status JSON API

The Public Server Status JSON API gives you access to live server statuses. This API is public and **does not require a key** as this data is cached every second.

## API Index

We currently offer the following public JSON APIs:

| API                  | Description                     | Documentation                                                         |
| -------------------- | ------------------------------- | --------------------------------------------------------------------- |
| `/status_one.json`   | CityDriving One Server Status   | [View Docs](/apis/public-json-api.md#server-status-citydriving-one)   |
| `/status_two.json`   | CityDriving Two Server Status   | [View Docs](/apis/public-json-api.md#server-status-citydriving-two)   |
| `/status_three.json` | CityDriving Three Server Status | [View Docs](/apis/public-json-api.md#server-status-citydriving-three) |
| `/status_four.json`  | CityDriving Four Server Status  | [View Docs](/apis/public-json-api.md#server-status-citydriving-four)  |

## Server Status: CityDriving One

**REQUEST:** `/json/status_one.json`

This request indexes players by InSim PLID (inside the `players` object) and returns all currently connected clients. It is designed for use with local InSim applications. This example only returns one client for brevity.

**RESPONSE:**

```
GET https://api.tc-gaming.co.uk/json/status_one.json
HTTP/1.1 200 OK
```

```javascript
{
    "server": "One",
    "time": 1490493497160,
    "players": {
        "17": {
            "siren": false,
            "med": false,
            "caution": false,
            "tow": false,
            "cop": false,
            "isChased": false,
            "isJoining": false,
            "hazard": false
        },
        ...
    }
}
```

## Server Status: CityDriving Two

**REQUEST:** `/json/status_two.json`

This request indexes players by InSim PLID (inside the `players` object) and returns all currently connected clients. It is designed for use with local InSim applications. This example only returns one client for brevity.

**RESPONSE:**

```
GET https://api.tc-gaming.co.uk/json/status_two.json
HTTP/1.1 200 OK
```

```javascript
{
    "server": "Two",
    "time": 1490493497160,
    "players": {
        "17": {
            "siren": false,
            "med": false,
            "caution": false,
            "tow": false,
            "cop": false,
            "isChased": false,
            "isJoining": false,
            "hazard": false
        },
        ...
    }
}
```

## Server Status: CityDriving Three

**REQUEST:** `/json/status_three.json`

This request indexes players by InSim PLID (inside the `players` object) and returns all currently connected clients. It is designed for use with local InSim applications. This example only returns one client for brevity.

**RESPONSE:**

```
GET https://api.tc-gaming.co.uk/json/status_three.json
HTTP/1.1 200 OK
```

```javascript
{
    "server": "Three",
    "time": 1490493497160,
    "players": {
        "17": {
            "siren": false,
            "med": false,
            "caution": false,
            "tow": false,
            "cop": false,
            "isChased": false,
            "isJoining": false,
            "hazard": false
        },
        ...
    }
}
```

## Server Status: CityDriving Four

**REQUEST:** `/json/status_four.json`

This request indexes players by InSim PLID (inside the `players` object) and returns all currently connected clients. It is designed for use with local InSim applications. This example only returns one client for brevity.

**RESPONSE:**

```
GET https://api.tc-gaming.co.uk/json/status_four.json
HTTP/1.1 200 OK
```

```javascript
{
    "server": "Four",
    "time": 1490493497160,
    "players": {
        "17": {
            "siren": false,
            "med": false,
            "caution": false,
            "tow": false,
            "cop": false,
            "isChased": false,
            "isJoining": false,
            "hazard": false
        },
        ...
    }
}
```


---

# 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://apidocs.tc-gaming.co.uk/apis/public-json-api.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.