/telnyx-numbers-python
Search, order, and manage phone numbers by location, features, and coverage.
$ npx -y skills add team-telnyx/ai --skill telnyx-numbers-python --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/telnyx-numbers-python
Context preview
The summary Claude sees to decide when to auto-load this skill.
Search, order, and manage phone numbers by location, features, and coverage.
SKILL.md
telnyx-numbers-python.SKILL.mdname: telnyx-numbers-python
description: >-
Search, order, and manage phone numbers by location, features, and coverage.
metadata:
author: telnyx
product: numbers
language: python
generated_by: telnyx-ext-skills-generator
profile: northstar-v2
<!-- Auto-generated from Telnyx OpenAPI specs. Do not edit. -->
Telnyx Numbers - Python
Installation
pip install telnyx
Setup
import os
from telnyx import Telnyx
client = Telnyx(
api_key=os.environ.get("TELNYX_API_KEY"), # This is the default and can be omitted
)All examples below assume `client` is already initialized as shown above.
Error Handling
All API calls can fail with network errors, rate limits (429), validation errors (422), or authentication errors (401). Always handle errors in production code:
import telnyx
try:
available_phone_numbers = client.available_phone_numbers.list()
except telnyx.APIConnectionError:
print("Network error — check connectivity and retry")
except telnyx.RateLimitError:
import time
time.sleep(1) # Check Retry-After header for actual delay
except telnyx.APIStatusError as e:
print(f"API error {e.status_code}: {e.message}")
if e.status_code == 422:
print("Validation error — check required fields and formats")Common error codes: `401` invalid API key, `403` insufficient permissions, `404` resource not found, `422` validation error (check field formats), `429` rate limited (retry with exponential backoff).
Important Notes
- **Phone numbers** must be in E.164 format (e.g., `+13125550001`). Include the `+` prefix and country code. No spaces, dashes, or parentheses.
- **Pagination:** List methods return an auto-paginating iterator. Use `for item in page_result:` to iterate through all pages automatically.
Reference Use Rules
Do not invent Telnyx parameters, enums, response fields, or webhook fields.
- If the parameter, enum, or response field you need is not shown inline in this skill, read [references/api-details.md](references/api-details.md) before writing code.
- Before using any operation in `## Additional Operations`, read [the optional-parameters section](references/api-details.md#optional-parameters) and [the response-schemas section](references/api-details.md#response-schemas).
Core Tasks
Search available phone numbers
Number search is the entrypoint for provisioning. Agents need the search method, key query filters, and the fields returned for candidate numbers.
`client.available_phone_numbers.list()` — `GET /available_phone_numbers`
| Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `filter` | object | No | Consolidated filter parameter (deepObject style). |
available_phone_numbers = client.available_phone_numbers.list()
print(available_phone_numbers.data)
Response wrapper:
- items: `available_phone_numbers.data`
- pagination: `available_phone_numbers.meta`
Primary item fields:
- `phone_number`
- `record_type`
- `quickship`
- `reservable`
- `best_effort`
- `cost_information`
Create a number order
Number ordering is the production provisioning step after number selection.
`client.number_orders.create()` — `POST /number_orders`
| Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `phone_numbers` | array[object] | Yes | | | `connection_id` | string (UUID) | No | Identifies the connection associated with this phone number. | | `messaging_profile_id` | string (UUID) | No | Identifies the messaging profile associated with the phone n... | | `billing_group_id` | string (UUID) | No | Identifies the billing group associated with the phone numbe... | | ... | | | +1 optional params in [references/api-details.md](references/api-details.md) |
number_order = client.number_orders.create(
phone_numbers=[{"phone_number": "+18005550101"}],
)
print(number_order.data)Primary response fields:
- `number_order.data.id`
- `number_order.data.status`
- `number_order.data.phone_numbers_count`
- `number_order.data.requirements_met`
- `number_order.data.messaging_profile_id`
- `number_order.data.connection_id`
Check number order status
Order status determines whether provisioning completed or additional requirements are still blocking fulfillment.
`client.number_orders.retrieve()` — `GET /number_orders/{number_order_id}`
| Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `number_order_id` | string (UUID) | Yes | The number order ID. |
number_order = client.number_orders.retrieve(
"number_order_id",
)
print(number_order.data)Primary response fields:
- `number_order.data.id`
- `number_order.data.status`
- `number_order.data.requirements_met`
- `number_order.data.phone_numbers_count`
- `number_order.data.phone_numbers`
- `number_order.data.connection_id`
---
Important Supporting Operations
Use these when the core tasks above are close to your flow, but you need a common variation or follow-up step.
Create a number reservation
Create or provision an additional resource when the core tasks do not cover this flow.
`client.number_reservations.create()` — `POST /number_reservations`
| Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `phone_numbers` | array[object] | Yes | | | `status` | enum (pending, success, failure) | No | The status of the entire reservation. | | `id` | string (UUID) | No | | | `record_type` | string | No | | | ... | | | +3 optional params in [references/api-details.md](references/api-details.md) |
number_reservation = client.number_reservations.create(
phone_numbers=[{"phone_number": "+18005550101"}],
)
print(number_reservation.data)Primary response fields:
- `number_reservation.data.id`
- `number_reservation.data.status`
- `number_reservation.data.created_at`
- `number_reservation.data.updated_at`
- `n
Read more
name: telnyx-numbers-python description: >- Search, order, and manage phone numbers by location, features, and coverage. metadata: author: telnyx product: numbers language: python generated_by: telnyx-ext-skills-generator profile: northstar-v2
<!-- Auto-generated from Telnyx OpenAPI specs. Do not edit. -->
Telnyx Numbers - Python
Installation
pip install telnyx
Setup
import os
from telnyx import Telnyx
client = Telnyx(
api_key=os.environ.get("TELNYX_API_KEY"), # This is the default and can be omitted
)All examples below assume `client` is already initialized as shown above.
Error Handling
All API calls can fail with network errors, rate limits (429), validation errors (422), or authentication errors (401). Always handle errors in production code:
import telnyx
try:
available_phone_numbers = client.available_phone_numbers.list()
except telnyx.APIConnectionError:
print("Network error — check connectivity and retry")
except telnyx.RateLimitError:
import time
time.sleep(1) # Check Retry-After header for actual delay
except telnyx.APIStatusError as e:
print(f"API error {e.status_code}: {e.message}")
if e.status_code == 422:
print("Validation error — check required fields and formats")Common error codes: `401` invalid API key, `403` insufficient permissions, `404` resource not found, `422` validation error (check field formats), `429` rate limited (retry with exponential backoff).
Important Notes
- **Phone numbers** must be in E.164 format (e.g., `+13125550001`). Include the `+` prefix and country code. No spaces, dashes, or parentheses.
- **Pagination:** List methods return an auto-paginating iterator. Use `for item in page_result:` to iterate through all pages automatically.
Reference Use Rules
Do not invent Telnyx parameters, enums, response fields, or webhook fields.
- If the parameter, enum, or response field you need is not shown inline in this skill, read [references/api-details.md](references/api-details.md) before writing code.
- Before using any operation in `## Additional Operations`, read [the optional-parameters section](references/api-details.md#optional-parameters) and [the response-schemas section](references/api-details.md#response-schemas).
Core Tasks
Search available phone numbers
Number search is the entrypoint for provisioning. Agents need the search method, key query filters, and the fields returned for candidate numbers.
`client.available_phone_numbers.list()` — `GET /available_phone_numbers`
| Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `filter` | object | No | Consolidated filter parameter (deepObject style). |
available_phone_numbers = client.available_phone_numbers.list() print(available_phone_numbers.data)
Response wrapper:
- items: `available_phone_numbers.data`
- pagination: `available_phone_numbers.meta`
Primary item fields:
- `phone_number`
- `record_type`
- `quickship`
- `reservable`
- `best_effort`
- `cost_information`
Create a number order
Number ordering is the production provisioning step after number selection.
`client.number_orders.create()` — `POST /number_orders`
| Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `phone_numbers` | array[object] | Yes | | | `connection_id` | string (UUID) | No | Identifies the connection associated with this phone number. | | `messaging_profile_id` | string (UUID) | No | Identifies the messaging profile associated with the phone n... | | `billing_group_id` | string (UUID) | No | Identifies the billing group associated with the phone numbe... | | ... | | | +1 optional params in [references/api-details.md](references/api-details.md) |
number_order = client.number_orders.create(
phone_numbers=[{"phone_number": "+18005550101"}],
)
print(number_order.data)Primary response fields:
- `number_order.data.id`
- `number_order.data.status`
- `number_order.data.phone_numbers_count`
- `number_order.data.requirements_met`
- `number_order.data.messaging_profile_id`
- `number_order.data.connection_id`
Check number order status
Order status determines whether provisioning completed or additional requirements are still blocking fulfillment.
`client.number_orders.retrieve()` — `GET /number_orders/{number_order_id}`
| Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `number_order_id` | string (UUID) | Yes | The number order ID. |
number_order = client.number_orders.retrieve(
"number_order_id",
)
print(number_order.data)Primary response fields:
- `number_order.data.id`
- `number_order.data.status`
- `number_order.data.requirements_met`
- `number_order.data.phone_numbers_count`
- `number_order.data.phone_numbers`
- `number_order.data.connection_id`
---
Important Supporting Operations
Use these when the core tasks above are close to your flow, but you need a common variation or follow-up step.
Create a number reservation
Create or provision an additional resource when the core tasks do not cover this flow.
`client.number_reservations.create()` — `POST /number_reservations`
| Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `phone_numbers` | array[object] | Yes | | | `status` | enum (pending, success, failure) | No | The status of the entire reservation. | | `id` | string (UUID) | No | | | `record_type` | string | No | | | ... | | | +3 optional params in [references/api-details.md](references/api-details.md) |
number_reservation = client.number_reservations.create(
phone_numbers=[{"phone_number": "+18005550101"}],
)
print(number_reservation.data)Primary response fields:
- `number_reservation.data.id`
- `number_reservation.data.status`
- `number_reservation.data.created_at`
- `number_reservation.data.updated_at`
- `n
This repo is the one-stop shop for AI Agents and AI-first developers building with Telnyx — everything an agent needs to build production-grade applications and manage its account, from signup to funding.
Repo: team-telnyx/ai
Other skills on team-telnyx-ai.
- /telnyx-ai-assistants-curl
AI voice assistants with custom instructions, knowledge bases, and tool integrations.
Open skill - /telnyx-ai-assistants-go
AI voice assistants with custom instructions, knowledge bases, and tool integrations.
Open skill - /telnyx-ai-assistants-java
AI voice assistants with custom instructions, knowledge bases, and tool integrations.
Open skill - /telnyx-ai-assistants-javascript
AI voice assistants with custom instructions, knowledge bases, and tool integrations.
Open skill - /telnyx-ai-assistants-python
AI voice assistants with custom instructions, knowledge bases, and tool integrations.
Open skill - /telnyx-ai-assistants-ruby
AI voice assistants with custom instructions, knowledge bases, and tool integrations.
Open skill

