Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.telegent.com/llms.txt

Use this file to discover all available pages before exploring further.

Version: 1.0.2.3 · Published: May 27, 2026 · Published by: Telegent Platform Team
This release enriches the Best Practices reference guide with response payload examples for every major API call across Sections 4–10, so you can see exactly what each endpoint returns before writing integration code. The number provisioning walkthrough (Section 8.1) also receives expanded step-by-step context.

Enhanced

Every key API call in the Best Practices reference guide now shows both the request and the response in a tabbed code block. Previously, only request bodies were shown. The following sections are updated:
SectionEndpoints with new response examples
4 — RoutesCreate Message Route, Create Voice Route
5 — Products & PackagesCreate Product, Create Package, Add Package Item
6 — SubscriptionsCreate Subscription
7 — Number ProvisioningCheck Availability, Provision Number
8 — Port-In LifecycleCheck Eligibility, Submit Port-In, Update Port-In, Cancel Port-In, Check Order Status, Port-Out
9 — Data Usage ControlsSet Data Usage Rules
10 — AI GuardianEnable Guardian Features, Create Call Filter, Add Allowed/Blocked Numbers, Create Message Filter, Add Allowed/Blocked Contacts
Response examples include the full object returned — IDs, status fields, and all populated properties — giving you a reliable reference for what to parse and store after each call.
Steps 1 and 2 of the number provisioning walkthrough now explain what each call does, what to look for in the response, and how to carry the result into the next step:
  • Step 1 (Check Availability): Clarifies that AvailableNumberAreas returns NGP and AreaCode pairs with live inventory, and that PageNumber can be used to paginate if your target area code doesn’t appear on the first page.
  • Step 2 (Provision): Explains that the response returns PhoneNumberId (the NID- identifier) and PhoneNumberAssigned (the E.164 number), and that both should be saved for use in subscriptions, data usage settings, and route updates.

If you have questions about any of these changes, contact support@telegent.com.