> For the complete documentation index, see [llms.txt](https://docs.monolithforensics.com/monolith/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monolithforensics.com/monolith/monolith-api-and-webhooks/api-access/api-endpoints.md).

# API Endpoints

Find the Monolith API base URL for your cloud region, partner environment, or on-premises deployment.

Monolith API requests must be sent to the API endpoint associated with the environment where your Monolith tenant is hosted.

Cloud API endpoints use the `/api/v1` path appended to the corresponding Monolith application URL.

### Cloud API Endpoints

| Region                                   | API Base URL                                          |
| ---------------------------------------- | ----------------------------------------------------- |
| **United States / North America**        | `https://monolith-app.monolithforensics.com/api/v1`   |
| **Australia**                            | `https://monolith-syd.monolithforensics.com/api/v1`   |
| **Canada**                               | `https://monolith-can.monolithforensics.com/api/v1`   |
| **United Kingdom / Blue Lights Digital** | `https://monolith-app.bluelightsdigital.com/api/v1`   |
| **United Kingdom / Europe**              | `https://monolith-app.monolithforensics.co.uk/api/v1` |

Use the endpoint that corresponds to the Monolith environment your organization normally accesses.

{% hint style="info" %}
**Blue Lights Digital** is a Monolith partner environment for supported customers in the United Kingdom. If your organization accesses Monolith through Blue Lights Digital, use the corresponding Blue Lights Digital API endpoint.
{% endhint %}

See [**Accessing Monolith**](/monolith/start-here/welcome-to-monolith/accessing-monolith.md) for the corresponding Monolith application URLs and additional information about available cloud regions.

### On-Premises API Endpoints

Organizations that self-host Monolith should use the hostname, IP address, or custom domain configured for their on-premises deployment.

The API base URL follows the same `/api/v1` structure.

Examples:

```
https://192.168.1.22/api/v1
```

```
https://monolith.example.org/api/v1
```

The exact address depends on how your organization has configured DNS, networking, TLS, and access to the Monolith server.

See [**On-Premises Deployments**](/monolith/deployment-and-security/on-premises-deployments.md) for additional deployment guidance.

### Using the Base URL

Resource endpoints are added after the `/api/v1` base URL.

For example, using the United States / North America environment:

```
https://monolith-app.monolithforensics.com/api/v1/info
```

corresponds to:

```
GET /api/v1/info
```

See [**Authentication**](/monolith/monolith-api-and-webhooks/api-access/authentication.md) for information about authenticating API requests and [**Info API**](/monolith/monolith-api-and-webhooks/info-api.md) for a simple endpoint you can use to verify API access.

### Related Documentation

* [**API Access**](/monolith/monolith-api-and-webhooks/api-access.md)
* [**Authentication**](/monolith/monolith-api-and-webhooks/api-access/authentication.md)
* [**Info API**](/monolith/monolith-api-and-webhooks/info-api.md)
* [**Accessing Monolith**](/monolith/start-here/welcome-to-monolith/accessing-monolith.md)
* [**On-Premises Deployments**](/monolith/deployment-and-security/on-premises-deployments.md)