diff --git a/site/specs-temp/numbers.json b/site/specs-temp/numbers.json
index 1611db82a..8839c5adc 100644
--- a/site/specs-temp/numbers.json
+++ b/site/specs-temp/numbers.json
@@ -3098,7 +3098,7 @@
"/accounts/{accountId}/discnumbers": {
"get": {
"tags": [
- "/accounts"
+ "Disconnecting Numbers"
],
"description": "Retrieves a list of disconnected numbers associated with the account. There are optional search parameters to limit the discNumbers payload",
"operationId": "GetDisconnectedTns",
@@ -3171,7 +3171,7 @@
"/accounts/{accountId}/discnumbers/totals": {
"get": {
"tags": [
- "/accounts"
+ "Disconnecting Numbers"
],
"description": "Retrieves a total number of disconnects.",
"operationId": "GetTotalNumberDisconnects",
@@ -3223,7 +3223,7 @@
"/accounts/{accountId}/disconnects": {
"get": {
"tags": [
- "/accounts"
+ "Disconnecting Numbers"
],
"description": "Retrieve a list of disconnect orders that is associated with an account.\nPlease visit Guides and Tutorials",
"summary": "Read disconnect orders",
@@ -3330,7 +3330,7 @@
"post": {
"description": "Use this method to disconnect telephone numbers from the account. Please visit Guides and Tutorials",
"tags": [
- "/accounts"
+ "Disconnecting Numbers"
],
"summary": "Disconnect numbers from account",
"operationId": "CreateDisconnectOrder",
@@ -3393,7 +3393,7 @@
"/accounts/{accountId}/disconnects/{disconnectid}": {
"get": {
"tags": [
- "/accounts"
+ "Disconnecting Numbers"
],
"description": "Retrieves the information associated with the disconnect order specified.\nPlease visit Guides and Tutorials",
"operationId": "ReadDisconnectOrder",
@@ -3447,7 +3447,7 @@
"/accounts/{accountId}/disconnects/{disconnectid}/notes": {
"get": {
"tags": [
- "/accounts"
+ "Disconnecting Numbers"
],
"description": "Retrieve all notes associated with the disconnect order. Please visit Guides and Tutorials",
"operationId": "ReadDisconnectOrderNotes",
@@ -3491,7 +3491,7 @@
},
"post": {
"tags": [
- "/accounts"
+ "Disconnecting Numbers"
],
"description": "Updates the Notes resource by adding a note. Adding a note to a disconnect \n order causes a notification to be sent to Bandwidth Operations, so that they may assist as necessary. A note may be up to 500 characters in length. Please visit Guides and Tutorials",
"operationId": "CreateDisconnectOrderNote",
@@ -3552,7 +3552,7 @@
"/accounts/{accountId}/disconnects/{disconnectid}/notes/{noteId}": {
"put": {
"tags": [
- "/accounts"
+ "Disconnecting Numbers"
],
"description": "Update a specified note. Notes may only be updated, not deleted. Please visit Guides and Tutorials\n",
"operationId": "UpdateDisconnectOrderNote",
@@ -4368,7 +4368,7 @@
"/accounts/{accountId}/emergencyNotificationRecipients": {
"get": {
"tags": [
- "/accounts"
+ "Emergency Notification"
],
"description": "Retrieve a list of emergency notification recipients configured for this account.
\n Results can be paginated and filtered using the following query parameters.",
"operationId": "ListEmergencyNotificationRecipients",
@@ -4530,7 +4530,7 @@
},
"post": {
"tags": [
- "/accounts"
+ "Emergency Notification"
],
"description": "Create a new emergency notification recipient.",
"summary": "Create emergency notification recipient",
@@ -4655,7 +4655,7 @@
"/accounts/{accountId}/emergencyNotificationRecipients/{enrId}": {
"get": {
"tags": [
- "/accounts"
+ "Emergency Notification"
],
"description": "The GET operation is used to fetch the emergency notification recipient specified by its identifier.
\nURI parameters:
Query parameters:
\nThe GET operation has no request payload, but the accountId must be specified in the URI parameter.\nResults are returned in the order of newest to oldest modification date of the Emergency Notification Group.\nQuery parameters act as filters on the data. If more than one query parameter is provided, the results will be the intersection of the results from each query parameter. In other words, the query parameters are logically ANDed.\nQuery parameters are appended to the end of the endpoint, separated by a '?' and in the format parameter=value. If you wish to specify more than one query parameter, separate them using an '&' character.\n The order of query parameters does not matter",
"operationId": "ListEmergencyNotificationGroups",
@@ -5461,7 +5461,7 @@
"/accounts/{accountId}/emergencyNotificationGroups/{engId}": {
"get": {
"tags": [
- "/accounts"
+ "Emergency Notification"
],
"description": "This endpoint allows you to fetch the configuration of a current emergency notification group by identifier.",
"operationId": "RetrieveEmergencyNotificationGroup",
@@ -5564,7 +5564,7 @@
"/accounts/{accountId}/emergencyNotificationEndpointOrders": {
"get": {
"tags": [
- "/accounts"
+ "Emergency Notification"
],
"description": "The GET operation provides a means to query any Emergency Notification Endpoint Order associated with the account. This endpoint is for querying \"orders\", not the emergency endpoint to emergency notification group associations themselves. \n
The GET operation has no payload, although the accountId URI parameter is mandatory and a number of optional query parameters may be added. The query parameters are described in this section.\n Results are returned by default in the order of newest to oldest creation date of the Emergency Notification Endpoint Order. This default order is reversed from oldest to newest when the CreatedAfterDate query parameter is included in the query.\n Query parameters act as filters on the data. If more than one query parameter is provided, the results will be the intersection of the results from each query parameter. In other words, the query parameters are logically ANDed.\n Query parameters are appended to the end of the endpoint, separated by a '?' and in the format parameter=value. If you wish to specify more than one query parameter, separate them using an '&' character. The order of query parameters does not matter",
"operationId": "ListEmergencyNotificationEndpointOrders",
@@ -5735,7 +5735,7 @@
},
"post": {
"tags": [
- "/accounts"
+ "Emergency Notification"
],
"description": "The POST operation creates a new order to request that an emergency endpoint be added to or removed from an emergency notification group. A given order may either add or remove associations, not both in one order.
\n If the order is successfully created, a 201 response is returned, including an order-id that is used to query for completion of the order.
\n The order's ProcessingStatus is set to PROCESSING when the request is successfully created. When processing of all emergency endpoint to emergency notification group associations has been attempted, the software\n will update the order's processing status to either COMPLETED or FAILED.",
"operationId": "CreateEmergencyNotificationEndpointOrder",
@@ -5836,7 +5836,7 @@
"/accounts/{accountId}/emergencyNotificationEndpointOrders/{orderId}": {
"get": {
"tags": [
- "/accounts"
+ "Emergency Notification"
],
"description": "This endpoint is used to fetch the status of an emergency notification endpoint order, using the order-id assigned when the order was created.
\nIf the order is still being processed, the ProcessingStatus will be PROCESSING. If the order has completed successfully, the ProcessingStatus will be COMPLETED. Otherwise the ProcessingStatus will be FAILED. If the ProcessingStatus is FAILED, look for the ErrorList in the payload to see reasons for the failure.\nURI parameters:
Retrieve a list of the externalTns orders that are associated with the account.
A maximum of 1,000 orders can be retrieved per request. If no date range or specific query parameter (marked by * below) is provided, the order results will be limited to the last two years.
", "operationId": "ListExternalTnsOrder", @@ -6049,7 +6049,7 @@ }, "post": { "tags": [ - "/accounts" + "External Tn" ], "description": "Create a externalTns order to add or remove telephone numbers provided by the customer from the Bandwidth network.
Note: the attempt to import a telephone number that is already present in the account will not create an error, but will reset all of the attributes of that telephone number in the Dashboard system as if the telephone number was being imported for the first time.
", "operationId": "CreateExternalTnsOrder", @@ -6110,7 +6110,7 @@ "/accounts/{accountId}/externalTns/{orderid}": { "get": { "tags": [ - "/accounts" + "External Tn" ], "description": "Retrieve information about a externalTns order with specified ID.
", "operationId": "GetExternalTnsOrder", @@ -6166,7 +6166,7 @@ "/accounts/{accountId}/geocodeRequest": { "post": { "tags": [ - "/accounts" + "Addresses" ], "description": "POST is used to validate address as geocode-able one. Request payload is the address to geocode. If decomposed elements are provided for AddressLine 1 then AddressLine1 is ignored. At least HouseNumber and StreetName are required to use them as replacement of AddressLine1. If at least HouseNumber or StreetName is absent then AddressLine1 is used.", "operationId": "CreateGeocodeRequest", @@ -6324,7 +6324,7 @@ "/accounts/{accountId}/importTnChecker": { "post": { "tags": [ - "/accounts" + "Import Tn" ], "description": "Request portability information on a set of TNs. SipPeerId is an optional value. If SipPeerId is not specified, the id of the default Sip-Peer for the provided SiteId will be used.
", "operationId": "CreateRequestImportTnChecker", @@ -6386,7 +6386,7 @@ "/accounts/{accountId}/importTnOrders": { "get": { "tags": [ - "/accounts" + "Import Tn" ], "description": "Retrieves the importtnorders requests for the given account ID. A maximum of 1,000 orders can be retrieved per request. If no date range or specific query parameter (marked by * below) is provided, the order results will be limited to the last two years.\n", "summary": "List Import Tn orders", @@ -6504,7 +6504,7 @@ }, "post": { "tags": [ - "/accounts" + "Import Tn" ], "description": "Creates an importTnOrders request to add numbers under the given site ID and sippeer ID as specified in the body.\nA successfully submitted order will have a status of \"RECEIVED\". A successfully completed order will have a status of \"COMPLETE\" if all of the telephone numbers were successfully imported and \"PARTIAL\" if some of the telephone numbers were imported. A failed order with will have a staus of \"FAILED\" and no telephone numbers would have been imported.", "summary": "Import Tn order", @@ -6565,7 +6565,7 @@ "/accounts/{accountId}/importTnOrders/{orderId}": { "get": { "tags": [ - "/accounts" + "Import Tn" ], "description": "Retrieve information about a importTnOrder with specified ID.", "summary": "Fetch Import Tn order status", @@ -6607,7 +6607,7 @@ "/accounts/{accountId}/importTnOrders/{orderId}/history": { "get": { "tags": [ - "/accounts" + "Import Tn" ], "description": "Retrieves the history of the specified importTnOrder.", "summary": "Fetch Import Tn order history", @@ -6649,7 +6649,7 @@ "/accounts/{accountId}/importTnOrders/{orderId}/loas": { "get": { "tags": [ - "/accounts" + "Import Tn" ], "description": "Retrieves the list of the loa (and other) files associated with the order.", "summary": "Fetch Import Tn order loas", @@ -6699,7 +6699,7 @@ }, "post": { "tags": [ - "/accounts" + "Import Tn" ], "description": "POSTing to the /loas resource will enable the upload of the file. The key attribute to the POST is ensuring that the headers are correctly set to support the file upload.A POST on the /subscriptions resource is used to request a new subscriptions for an account. The POST creates a new e-mail or callback subscription. A well-formed POST will create a subscription resource, and return a subscription ID as part of the location header. The ID is used to uniquely identify the subscription. The user should submit the desired e-mail address for notifications and the frequency with which he wants to get the updates: DAILY (for daily digests) or NONE (immediately after events). OrderId is optional. If OrderId is specified only notifications will be sent for events related to that order. If OrderId is omitted, notifications will be sent related to events of all orders of the specified type.
The credentials used to impose security on the callbacks are defined in the When status changes on an order that had been subscribed to with a callback subscription (order update, note added to order), the following payload will be POSTed to the URL of the callback subscription. More detail can be found in the API documentation for the fictitious endpoint /callbacks When a event happens that had been subscribed to with a callback subscription (messaging lost, messaging gained etc.), the following payload will be POSTed to the URL of the callback subscription. More detail can be found in the API documentation for the fictitious endpoint /callbacks",
"operationId": "CreateSubscriptions",
@@ -17198,7 +17198,7 @@
"/accounts/{accountId}/subscriptions/{subscriptionid}": {
"get": {
"tags": [
- "/accounts"
+ "Subscriptions"
],
"description": " Retrieves the information associated with the subscription ID.\nThe returned information reflects the subscription as it has been defined, and for callback subscriptions will reflect the status of the latest attempt to place the callback. The
Attribute description:
",
"operationId": "CreateTnOptionOrder",
@@ -17595,7 +17595,7 @@
"/accounts/{accountId}/tnoptions/{orderid}": {
"get": {
"tags": [
- "/accounts"
+ "Tn Option"
],
"description": "Retrieve information about a TN Option Order with specified ID.",
"operationId": "GetTnOptionOrder",
@@ -17651,7 +17651,7 @@
"/accounts/{accountId}/tnoptions/{orderid}/history": {
"get": {
"tags": [
- "/accounts"
+ "Tn Option"
],
"description": "Retrieve the history information associated with an order.",
"operationId": "GetOrderHistory",
@@ -33648,6 +33648,28 @@
"url": "/docs/emergency/dashboard/dlr/"
}
},
+ {
+ "name": "Disconnecting Numbers",
+ "description": "Disconnecting a phone number leaves it in all applicable inventories, but makes it available for activation with a new subscriber.",
+ "externalDocs": {
+ "description": "Disconnecting number guide",
+ "url": "/docs/numbers/guides/disconnectNumbers/"
+ }
+ },
+ {
+ "name": "Emergency Notification",
+ "description": "Emergency notifications are designed to support notification of front-desk personnel in the event that someone dials an emergency call from a multi-line telephone system (MLTS).",
+ "externalDocs": {
+ "description": "Emergency notification guide",
+ "url": "/docs/emergency/dashboard/notifications/"
+ }
+ },
+ {
+ "name": "External Tn"
+ },
+ {
+ "name": "Import Tn"
+ },
{
"name": "LIDB",
"description": "LIDB - Line Information DataBase",
@@ -33674,6 +33696,26 @@
"url": "/docs/numbers/guides/downloadingReports/"
}
},
+ {
+ "name": "Sip Registrar",
+ "externalDocs": {
+ "description": "Sip Registrar guide",
+ "url": "/docs/account/sipRegistrar/#create-sip-credentials"
+ }
+ },
+ {
+ "name": "SipPeer products"
+ },
+ {
+ "name": "Subscriptions",
+ "externalDocs": {
+ "description": "Subscriptions details",
+ "url": "/docs/account/subscriptions/"
+ }
+ },
+ {
+ "name": "Tn Option"
+ },
{
"name": "Tns"
},
Number attribute Action value Description of action LongCode systemDefault Removes the per-TN A2P attributes, and it reverts to the Location/SIP Peer characteristics. Any values for Class or Campaign ID are not valid LongCode asSpecified Sets the message class and campaign ID - this is the default if unspecified LongCode off Will set the TN as a 'P' TN. Any values for Class or Campaign ID are not valid LongCode delete Will delete the campaign ID from TN. Any values for Class or Campaign ID are not valid LongCode unchanged Do nothing with respect to A2P TollFree systemDefault Removes the per-TN A2P attributes, and it reverts to the Location/SIP Peer characteristics. Any values for Class or Campaign ID are not valid TollFree asSpecified Sets the message class and campaign ID - this is the default if unspecified TollFree off If the Togglz value is set to 'on' this is invalid for Toll Free telephone numbers. Any values for Class or Campaign ID in the payload are invalid. If the Togglz value is set to off this behaves like and A2P TN, where the characteristics of the TNs is set to 'P' TollFree unchanged Do nothing with respect to A2P Action value Description of action asSpecified Creates/updates the origination route plan for the TN with route plan details provided in the request off Removes the origination route plan for the TN. Route list is the request must be empty unchanged Doesn't update/create the origination route plan, even when route plan details exist in the request Action value Description of action true Enables Pindrop integration on each phone number in the option group false Explicitly disables Pindrop integration on each phone number in the option group