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 with func_id 0198c2c5-8f1e-7a3d-9b21-6e4a0d5f1c88 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
Custom domain support is available — see the Custom Domains guide to serve a function from your own domain with customer-provided TLS certificates.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