telnyx-voice-go_skill

Overview

This skill provides Go examples and patterns to make and receive calls, manage call lifecycle actions (answer, hangup, transfer, bridge), and work with Call Control applications and events. It focuses on Telnyx Voice call control operations and demonstrates how to initialize the SDK, manage connections, and handle webhook events. Examples are concise and ready to adapt into production call routing and telephony automation.

How this skill works

The skill shows how to initialize a Telnyx Go client and call API endpoints for dialing, answering, bridging, transferring, and hanging up calls. It also covers listing active calls for a connection, managing call control applications (create, retrieve, update, delete), and querying call events. Webhook guidance describes the event types delivered and the required headers for verification.

When to use it

• Build programmatic call flows from a Go backend that answers, dials, or bridges calls.
• Automate call lifecycle tasks like transfer, hangup, or bridging between endpoints.
• Manage call control applications and their webhook endpoints for dynamic routing.
• Monitor and archive call events for analytics, compliance, or debugging.
• List active calls per connection to display live call state in dashboards.

Best practices

• Initialize the Telnyx client once and reuse it across requests to avoid redundant setup.
• Validate and verify incoming webhooks using telnyx-timestamp and telnyx-signature-ed25519 headers.
• Use context.Context for request cancellation and timeouts in production services.
• Handle and log API errors explicitly; avoid panicking in production code paths.
• Limit sensitive data in logs and rotate API keys regularly.

Example use cases

• Answer an incoming call and immediately bridge it to an agent SIP endpoint.
• Dial outbound numbers from a specific connection and capture call events for billing.
• Transfer a live call to a different phone number or SIP URI during support escalation.
• Create and update call control applications to point webhooks at different microservices.
• List active calls for a connection to implement a supervisor monitoring UI.