> ## Documentation Index
> Fetch the complete documentation index at: https://developers.telnyx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Routes & Domains

> Every deployed function gets a public HTTPS URL — https://{func-name}-{org-nickname}.telnyxcompute.com — and HTTP requests to that URL are the only way a function is invoked.

Every function deployed with `telnyx-edge ship` gets a public HTTPS URL. Requests to that URL are the only trigger — there are no cron, queue, or event triggers today. If you need scheduled invocation, point an external scheduler (for example, a GitHub Actions cron job) at the URL.

## Public URL pattern

```
https://{func-name}-{org-nickname}.telnyxcompute.com
```

| Component      | Description                           |
| -------------- | ------------------------------------- |
| `func-name`    | The `func_name` from your `func.toml` |
| `org-nickname` | Your Telnyx organization's nickname   |

A function named `hello-world` in the organization `acme` is served at:

```
https://hello-world-acme.telnyxcompute.com
```

`telnyx-edge ship` prints the URL after a successful deploy:

```bash theme={null}
📡 Your function is live at:
   https://hello-world-acme.telnyxcompute.com

💡 Test your function:
   curl https://hello-world-acme.telnyxcompute.com
```

`telnyx-edge list` shows the invoke URL for every function in your organization.

## Calling your function

All HTTP methods and paths under the function's URL are routed to your server — path handling is up to your code (see [HTTP handler](/docs/edge-compute/runtime/http-handler)):

```bash theme={null}
# GET request
curl https://hello-world-acme.telnyxcompute.com

# POST request with JSON body
curl -X POST \
  -H "Content-Type: application/json" \
  -d '{"name": "test"}' \
  https://hello-world-acme.telnyxcompute.com/anything
```

Requests time out after 30 seconds by default (60 seconds maximum) — see [Limits](/docs/edge-compute/platform/limits).

## Custom domains

There is no custom domain support today — functions are reachable only at their `telnyxcompute.com` URL. To serve a function from your own domain, put a proxy you operate (CDN or reverse proxy) in front of it.

## Region placement

You can't pin a function to a region today; the platform chooses placement.

## Next Steps

* [HTTP handler](/docs/edge-compute/runtime/http-handler) — the entrypoint contract behind the URL
* [Versions & Rollback](/docs/edge-compute/configuration/versions) — the URL always points at the active revision
* [Limits](/docs/edge-compute/platform/limits) — request timeout and payload constraints