> For a complete index of all SignalWire documentation pages, fetch https://signalwire.com/docs/llms.txt

# Base URL

Every Space on SignalWire has its own subdomain, and every API request goes through your Space's subdomain over HTTPS. Plain HTTP requests are rejected.

```shell
https://{your_space}.signalwire.com
```

Throughout these docs, examples use the placeholder `example.signalwire.com` — replace `example` with your own Space's subdomain when copying requests into your code.

## Find your subdomain

Your Space subdomain is the prefix that comes before `.signalwire.com` in your Dashboard URL. If you sign in at `https://acme.signalwire.com/dashboard`, your subdomain is `acme`.

You'll also find it under **API Credentials** in the [SignalWire Dashboard](https://my.signalwire.com?page=credentials), alongside your Project ID and API tokens.

## URL structure

REST API requests follow a consistent pattern:

```shell
https://{your_space}.signalwire.com/api/{family}/{resource}
```

* **`{your_space}`** — your Space subdomain
* **`{family}`** — the API surface (e.g., `messaging`, `calling`, `fabric`)
* **`{resource}`** — the specific resource or operation (e.g., `messages`, `rooms`)

For example, listing messages for your project looks like:

```shell
https://example.signalwire.com/api/messaging/messages
```

## HTTPS only

All SignalWire REST APIs require HTTPS. Requests sent over plain HTTP are refused — there is no automatic upgrade. Make sure your HTTP client is configured for TLS.