v1.0.2.3

Response payloads added to Best Practices Sections 4–10

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:

Section	Endpoints with new response examples
4 — Routes	Create Message Route, Create Voice Route
5 — Products & Packages	Create Product, Create Package, Add Package Item
6 — Subscriptions	Create Subscription
7 — Number Provisioning	Check Availability, Provision Number
8 — Port-In Lifecycle	Check Eligibility, Submit Port-In, Update Port-In, Cancel Port-In, Check Order Status, Port-Out
9 — Data Usage Controls	Set Data Usage Rules
10 — AI Guardian	Enable 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.

Number provisioning steps now include descriptive context (Section 8.1)

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.

Release Notes

Enhanced

​Enhanced

Enhanced