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
A function named
hello-world in the organization acme is served at:
telnyx-edge ship prints the URL after a successful deploy:
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):Custom domains
There is no custom domain support today — functions are reachable only at theirtelnyxcompute.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 — the entrypoint contract behind the URL
- Versions & Rollback — the URL always points at the active revision
- Limits — request timeout and payload constraints