diff --git a/site/specs-temp/numbers.json b/site/specs-temp/numbers.json index 9f9290186..bf578110c 100644 --- a/site/specs-temp/numbers.json +++ b/site/specs-temp/numbers.json @@ -674,7 +674,7 @@ "/accounts/{accountId}/campaignManagement/10dlc/brands": { "get": { "tags": [ - "10 DLC" + "10DLC" ], "description": "Retrieve a list of campaign registry brands for the account", "operationId": "List brands", @@ -744,7 +744,7 @@ }, "post": { "tags": [ - "10 DLC" + "10DLC" ], "description": "

Create campaign registry brand on the Account

My Brand Note: Regardless of if you are a DirectCustomer or Reseller, you will need to create a 'My Brand'. You can only create one of these. On the Request Body you can indicate a 'My Brand' by setting the IsMain flag to true.

Please visit Brand and Reseller Management.

", "operationId": "Create brand", @@ -809,7 +809,7 @@ "/accounts/{accountId}/campaignManagement/10dlc/campaigns/imports": { "get": { "tags": [ - "10 DLC" + "10DLC" ], "description": "The GET method returns a list of Campaign Ids that have been imported into the account. The maximum number of Campaigns returned by this query is controlled by the size parameter. The page parameter can be used to fetch additional pages after the first.", "operationId": "GetImportedCampaigns", @@ -874,7 +874,7 @@ }, "post": { "tags": [ - "10 DLC" + "10DLC" ], "description": "The POST method is used to import a previously shared Campaign into the account.", "operationId": "ImportCampaign", @@ -938,7 +938,7 @@ "/accounts/{accountId}/campaignManagement/10dlc/campaigns/imports/{campaignId}": { "get": { "tags": [ - "10 DLC" + "10DLC" ], "description": "The GET method returns a сampaign that have been imported into the account.", "operationId": "GetImportedCampaign", @@ -1279,7 +1279,7 @@ "/accounts/{accountId}/bdrs": { "post": { "tags": [ - "/accounts" + "Reports" ], "description": "

Note - this API is being replaced with the /billingreports API - we strongly recommend that you use that endpoint.

This API allows the retrieval of a ZIP file containing BDR records for a specified date range. These BDR records are delivered as a ZIP compressed comma separated values (CSV) file. The general flow of the API calls required to retrieve these records is:

  1. POST a request to the /bdrs resource, describing the date range for which the BDR records are wished. This will initiate the construction of the zip file.
  2. Examine the response from the POST. If the payload is understandable and valid then a 202 accepted HTTP result code will be returned indicating that the response file is being created.
  3. Retrieve the Location Header from the Response to the POST. This location header will contain the resource ID for the collection of BDRs that will be returned once complete. Note that the fact that the ID has been issued does not mean that the ZIP file is complete.
  4. Interrogate the resource ID to check the status of the request. If a 303 See Other response is received then the Location Header will contain the resource path to the file. A typical browser response will be to download the file. If a 200 OK is returned then the request is considered valid, but the file is not ready for distribution.
  5. Fetching the file can be done by issuing a GET to the resources path in the Location Header mentioned above
", "deprecated": true, @@ -1341,7 +1341,7 @@ "/accounts/{accountId}/bdrs/{bdrid}": { "get": { "tags": [ - "/accounts" + "Reports" ], "deprecated": true, "description": "

The bdr id resource will query the status of the bdr file that is being generated. There are essentially two responses...

A GET on the BDR ID will return a still processing indication if the file creation has not completed, or will redirect to the file to be downloaded.

", @@ -1418,7 +1418,7 @@ "/accounts/{accountId}/bdrs/{bdrid}/file": { "get": { "tags": [ - "/accounts" + "Reports" ], "deprecated": true, "description": "A GET on the /file resource subtending a BDR ID will cause the download of the file. Executing this resource path within a browser will cause the download of the file.", @@ -1451,7 +1451,7 @@ "/accounts/{accountId}/billingreports": { "get": { "tags": [ - "/accounts" + "Reports" ], "description": "Retrieve billing report instances within the account scope and billing type. The valid Billing Types are...", "operationId": "GetBillingReportByType", @@ -1498,7 +1498,7 @@ }, "post": { "tags": [ - "/accounts" + "Reports" ], "description": "The payload for the POST declares the date range and type for the desired reports. The valid types are: \n", "operationId": "CreateBillingReport", @@ -1559,7 +1559,7 @@ "/accounts/{accountId}/billingreports/{reportid}": { "get": { "tags": [ - "/accounts" + "Reports" ], "description": "

The resource will query the status of the report that is being generated.

\n", "operationId": "GetBillingReportStatus", @@ -1630,7 +1630,7 @@ "/accounts/{accountId}/billingreports/{reportid}/file": { "get": { "tags": [ - "/accounts" + "Reports" ], "description": "

A GET on the /file resource subtending a report ID will cause the download of the file. Executing this resource path within a browser will cause the download of the file.

\n", "operationId": "DownloadBillingReport", @@ -1701,7 +1701,7 @@ "/accounts/{accountId}/bulkPortins": { "get": { "tags": [ - "Porting" + "Bulk Port-In" ], "description": "Retrieves bulk port-in orders for the specified accountId.\nA maximum of 1,000 orders can be retrieved per request. If no date range or specific query parameter is provided, the order results will be limited to the last two years. Please visit Guides and Tutorials", "operationId": "ListBulkPortins", @@ -1822,7 +1822,7 @@ }, "post": { "tags": [ - "Porting" + "Bulk Port-In" ], "description": "

Creates a bulk port-in order to be used as a template for a collection of child port-in orders. The template values will be cascaded to child port-ins that result from decomposing a collection of Telephone Numbers that span carriers, RespOrgs, or have attributes that drive the decomposition into a number of individual port-in orders.

Upon a successfully-submitted payload, the order will have a status of \"DRAFT\", denoting that further modification to the template is expected. For example, the next step is to use the /tnList endpoint to add a collection of telephone numbers to the bulk port-in order. The only valid value for the ProcessingStatus element in a POST is 'DRAFT', which is the default value.

Please visit Guides and Tutorials

", "operationId": "CreateBulkOrder", @@ -1883,7 +1883,7 @@ "/accounts/{accountId}/bulkPortins/{orderid}": { "get": { "tags": [ - "Porting" + "Bulk Port-In" ], "description": "Retrieves information associated with the bulk port-in order specified by the orderId URI parameter. Please visit Guides and Tutorials", "operationId": "RetrieveBulkOrder", @@ -1926,7 +1926,7 @@ }, "put": { "tags": [ - "Porting" + "Bulk Port-In" ], "description": "The PUT operation is available only for bulk port-in orders that are not yet associated with subtending orders. Since this only occurs for bulk port-in orders that are in one of the draft states, there are few restrictions on what may be included. As with the POST, any data associated with the bulk port-in will cascade to subtending orders when they are created. (Subtending orders are created after telephone numbers are added to the bulk port-in using the /tnList endpoint.) The PUT completely replaces the existing Bulk Portin order with the payload of the PUT. Please visit Guides and Tutorials.

The following element may appear only in PUT or PATCH operations on a bulk port-in order. ", "operationId": "PutBulkOrder", @@ -1994,7 +1994,7 @@ }, "delete": { "tags": [ - "Porting" + "Bulk Port-In" ], "description": "Delete a bulk port-in order with child port-ins. Deleting a bulk port-in is allowed for 'DRAFT' state only. Deleting a bulk port-in will delete all DRAFT child port-ins associated with the bulk port-in. When the bulk port-in is deleted, any child port-in orders that are not in a draft status are dissociated from the bulk port-in, but not deleted. Please visit Guides and Tutorials", "operationId": "DeleteBulkOrder", @@ -2037,7 +2037,7 @@ }, "patch": { "tags": [ - "Porting" + "Bulk Port-In" ], "description": "

It is possible to change (\"SUPP\" in LNP terms) an existing Bulk Port-in order. This is done via a PUT or PATCH on the existing order-id. Since the Bulk Port-in\n order acts as a template for port-in orders in DRAFT status, any record can be changed at any time. The PATCH replaces elements of the referenced Bulk Portin order, but it replaces only the records included in the request payload. Other elements will remain untouched.

Changing the fields in a Bulk Port-in order causes the system to reapply all changed values to the child port-ins contained in the list of subtending port-in orders. Note that if the port-in orders contained within the Bulk Port are in DRAFT state, any field can be modified. If any child port-in order in the Bulk Port-in is in any other state, normal SUPP rules apply, and the list of appropriate fields is smaller.

Changing the ProcessingStatus to 'IN_PROGRESS' causes all child port-ins to begin processing. This is only valid if child port-ins exist for the bulk port-in.

Please visit Guides and Tutorials

", "operationId": "PatchBulkOrder", @@ -2112,7 +2112,7 @@ "/accounts/{accountId}/bulkPortins/{orderid}/portinList": { "get": { "tags": [ - "Porting" + "Bulk Port-In" ], "description": "Retrieves a list of Port-in Orders that are all associated with the identified Bulk Port-in. This response is not paginated due to its inherently limited size. Please visit Guides and Tutorials", "operationId": "ListBulkChildOrders", @@ -2152,7 +2152,7 @@ }, "put": { "tags": [ - "Porting" + "Bulk Port-In" ], "description": "

A PUT on a PortinList resource will cause replacement of the list of port-in orders associated with the specified bulk port-in.

This PUT will completely replace the existing list of port-in orders associated with the bulk port-in. If all port-in orders in the list are not valid, the PUT request will fail, due to the potential for losing the port-in to bulk port-in relationships.

Only port-in orders in a draft status may be associated with a bulk port-in order. And port-in orders may only be added to a bulk port-in order while that bulk port-in order is still in a draft state.

Child port-in orders may be dissociated from the bulk port-in at any time.

Please visit Guides and Tutorials

", "operationId": "UpdateBulkChildList", @@ -2212,7 +2212,7 @@ "/accounts/{accountId}/bulkPortins/{orderid}/notes": { "get": { "tags": [ - "Porting" + "Bulk Port-In" ], "description": "Retrieve all notes associated with the order. Please visit Guides and Tutorials", "operationId": "ListBulkNotes", @@ -2255,7 +2255,7 @@ }, "post": { "tags": [ - "Porting" + "Bulk Port-In" ], "description": "Updates the Notes resource by adding a note. Adding a note to a port-in 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": "CreateBulkNote", @@ -2315,7 +2315,7 @@ "/accounts/{accountId}/bulkPortins/{orderid}/notes/{noteId}": { "put": { "tags": [ - "Porting" + "Bulk Port-In" ], "description": "Update a specified note. Notes may only be updated, not deleted. Please visit Guides and Tutorials", "operationId": "UpdateBulkNote", @@ -2385,7 +2385,7 @@ "/accounts/{accountId}/bulkPortins/{orderid}/tnList": { "get": { "tags": [ - "Porting" + "Bulk Port-In" ], "description": "

The information returned in the GET /tnList response payload depends on the ProcessingStatus of the bulk port-in order. See the Responses tab for examples of each response payload.

\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
\n

\n ProcessingStatus\n

\n 		\n

\n Information Returned\n

\n
\n

\n DRAFT\n

\n 		\n

\n In this state, no tnList has been provided, so the response\n includes empty portable and non-portable telephone number lists.\n

\n
\n

\n VALIDATE_DRAFT_TNS\n

\n 		\n

\n In this state, validation of the tnList is still in progress,\n so the response includes all of the tnList telephone numbers\n in a `not validated` list. This is a temporary state until\n the validation completes. Validation takes longer when toll\n free numbers are included in the tnList.\n

\n
\n

\n VALID_DRAFT_TNS\n

\n 		\n

\n In this state, all of the telephone numbers in the tnList have\n been determined to be portable. The response payload includes\n a list of the child port-in orders and shows which telephone\n numbers are assigned to each child port-in order.\n

\n
\n

\n INVALID_DRAFT_TNS\n

\n 		\n

\n In this state, at least one of the telephone numbers in the tnList\n has been determined to be non-portable. The response payload includes\n a list of portable numbers (if any) and a list of errors showing which\n telephone numbers are non-portable as well as the reasons why they\n cannot be ported. Or, if communication errors prevented us from\n determining telephone number portability, those errors will be included.\n

\n
\n

Please visit Guides and Tutorials

", "operationId": "ListBulkTns", @@ -2436,7 +2436,7 @@ }, "put": { "tags": [ - "Porting" + "Bulk Port-In" ], "description": "

This operation is used to add telephone numbers to a draft bulk port-in order.\n The telephone numbers may be a mix of toll free and non-toll free. Once the\n telephone numbers are added, they will be checked for portability, and if\n portable, decomposed into individual child port-in orders. Both the bulk\n port-in order and the child port-in orders remain in draft status until you\n explicitly submit them.

\n\n

After submitting a tnList with the PUT operation, you will need to poll for\n completion of the validation and decomposition using the GET /tnList operation\n or the GET /bulkPortins/orderId operation (both include the order ProcessingStatus).\n The basic ProcessingStatus flow is as follows:

\n\n\n

Please visit Guides and Tutorials

", "operationId": "UpdateBulkTnList", @@ -2509,7 +2509,7 @@ "/accounts/{accountId}/bulkPortins/{orderid}/history": { "get": { "tags": [ - "Porting" + "Bulk Port-In" ], "description": "Retrieves the history of the specified bulk port-in order. Obtaining history for a draft bulk port-in is not supported.

Please visit Guides and Tutorials

", "operationId": "GetBulkHistory", @@ -2570,7 +2570,7 @@ "/accounts/{accountId}/bulkPortins/{orderid}/loas": { "get": { "tags": [ - "Porting" + "Bulk Port-In" ], "description": "Retrieves the list of the loa (and other) files associated with the order.", "operationId": "ListBulkLoas", @@ -2621,7 +2621,7 @@ }, "post": { "tags": [ - "Porting" + "Bulk Port-In" ], "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.
\nQuery parameter or header documentType can be used to specify type of document on upload. Possible values are: LOA, INVOICE, CSR, OTHER.\n
\nHeader settings typical of a valid upload are...
\n
\n\nHost: dashboard.bandwidth.com
\nAuthorization: Basic xxxxxxxxxxxxxxxxxxxx==
\nContent-Type: application/pdf
\ndocumentType: [LOA | INVOICE | CSR | OTHER]
\nAccept: /
\nAccept-Encoding: gzip, deflate
\nAccept-Language: en-US,en;q=0.8
\nCache-Control: no-cache
\n
\n----WebKitFormBoundaryE19zNvXGzXaLvS5C
\nContent-Disposition: form-data; name=\"george\"; filename=\"Bandwidth Dashboard.pdf\"
\nContent-Type: application/pdf
\n
\n
\n----WebKitFormBoundaryE19zNvXGzXaLvS5C
\n

", "operationId": "UploadBulkLoa", @@ -3620,7 +3620,7 @@ "/accounts/{accountId}/dldas": { "get": { "tags": [ - "/accounts" + "DLDA" ], "description": "Retrieve a list of the DLDA 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": "ReadDldaOrders", @@ -3694,7 +3694,7 @@ }, "post": { "tags": [ - "/accounts" + "DLDA" ], "description": "Create DLDA order to associate the street address with the telephone number.
Business Listings
Business Listings sort differently than Residential Listings, and must be submitted accordingly. Since Business Listings sort starting at the beginning of the name, where Residential Listings sort on Last Name, the parts of the business name that will govern the sorting need to be entered in the LastName field. For example, Joe's Pizza sorts starting with Joe, so the entire business name would be entered in the LastName field, and the Firstname could be left blank. If there was a portion of the name that was not important from a sorting perspective (perhaps \"the best pizza in town\"), that portion could be placed in the FirstName field.", "operationId": "CreateDldaOrder", @@ -3758,7 +3758,7 @@ "/accounts/{accountId}/dldas/{orderid}": { "get": { "tags": [ - "/accounts" + "DLDA" ], "description": "Retrieve information about a DLDA Order with specified ID.", "operationId": "ReadDldaOrder", @@ -3815,7 +3815,7 @@ }, "put": { "tags": [ - "/accounts" + "DLDA" ], "description": "Update DLDA order to associate the street address with the telephone number.", "operationId": "UpdateDldaOrder", @@ -3889,7 +3889,7 @@ "/accounts/{accountId}/dldas/{orderid}/history": { "get": { "tags": [ - "/accounts" + "DLDA" ], "description": "Retrieve the history information associated with a named DLDA order. This indicates the various states that the order has passed through, as well as the current state of the order as the last entry.", "operationId": "ReadDldaOrderHistory", @@ -7720,7 +7720,7 @@ "/accounts/{accountId}/lidbs": { "get": { "tags": [ - "/accounts" + "LIDB" ], "description": "The LIDBs Resource represents the requests made to the Bandwidth Dashboard API to add or otherwise manage a request to add Calling Line Information with a telephone number. This API allows the creation and observation of a \"Line Information Data Base (LIDB)\" work order that causes an update of a person's calling name identification in a network Database. The entry of this information in the network database in turn causes the display of their name on the phone of the people that they call.\n\nGET /accounts/{accountId}/lidbs API call is used to retrieve information about outstanding LIDBs orders, and POST to create those orders. Retrieve a list of the LIDB 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": "ListLidbOrders", @@ -7794,7 +7794,7 @@ }, "post": { "tags": [ - "/accounts" + "LIDB" ], "description": "The LIDBs Resource represents the requests made to the Bandwidth Dashboard API to add or otherwise manage a request to add Calling Line Information with a telephone number. This API allows the creation and observation of a \"Line Information Data Base (LIDB)\" work order that causes an update of a person's calling name identification in a network Database. The entry of this information in the network database in turn causes the display of their name on the phone of the people that they call. \nThis API call supports GET to retrieve information about outstanding LIDBs orders, and POST to create those orders.\n\nCreate a LIDB order to associate Calling Name Information with a TN or list of TNs.", "operationId": "CreateLidbOrder", @@ -7858,7 +7858,7 @@ "/accounts/{accountId}/lidbs/{lidbid}": { "get": { "tags": [ - "/accounts" + "LIDB" ], "description": "The LIDBs Resource represents the requests made to the Bandwidth Dashboard API to add or otherwise manage a request to add Calling Line Information with a telephone number. This API allows the creation and observation of a \"Line Information Data Base (LIDB)\" work order that causes an update of a person's calling name identification in a network Database. The entry of this information in the network database in turn causes the display of their name on the phone of the people that they call. \nThis API call supports GET to retrieve information about outstanding LIDBs orders, and POST to create those orders.\n\nRetrieve information about a specific Lidb Order identified as the resource.\nThe LIDBs Resource represents the requests made to the Bandwidth Dashboard API to add or otherwise manage a request to add Calling Line Information with a telephone number. This API allows the creation and observation of a \"Line Information Data Base (LIDB)\" work order that causes an update of a person's calling name identification in a network Database. The entry of this information in the network database in turn causes the display of their name on the phone of the people that they call. \nThis API call supports GET to retrieve information about outstanding LIDBs orders, and POST to create those orders.", "operationId": "ReadLidbOrder", @@ -9835,6 +9835,7 @@ ], "responses": { "200": { + "description": "", "content": { "application/xml": { "examples": { @@ -11250,6 +11251,7 @@ ], "responses": { "200": { + "description": "", "content": { "application/xml": { "schema": { @@ -11571,6 +11573,7 @@ ], "responses": { "200": { + "description": "", "content": { "application/xml": { "schema": { @@ -11587,8 +11590,8 @@ "tags": [ "Porting" ], - "description": "Retrieves the total count of port-ins.", - "operationId": "RetrievePortinTotals", + "description": "Retrieves the total count of port-uts.", + "operationId": "RetrievePortOutTotals", "summary": "Retrieve total count of port-in orders", "parameters": [ { @@ -11596,7 +11599,7 @@ }, { "name": "status", - "description": "The current status of the port-in.", + "description": "The current status of the port-out.", "in": "query", "required": false, "schema": { @@ -11606,7 +11609,7 @@ }, { "name": "vendorId", - "description": "The vendor ID of the port-in.", + "description": "The vendor ID of the port-out.", "in": "query", "required": false, "schema": { @@ -12936,7 +12939,7 @@ "/accounts/{accountId}/reports": { "get": { "tags": [ - "/accounts" + "Reports" ], "description": "Retrieves a list of the report templates available for use within the Bandwidth Dashboard API. This list contains the basic description of the reports, including a report ID that can be used to access further details about the report, and thus facilitating the subsequent choice and creation of an instance of the report. Items of this list are sorted by display priority in ascending order and alphabetically by name within priority groups (display priority is displayed only for admin endpoint)", "summary": "List Reports", @@ -12968,7 +12971,7 @@ "/accounts/{accountId}/reports/{reportId}": { "get": { "tags": [ - "/accounts" + "Reports" ], "description": "Retrieve a specific report with all of the details. Allowing to create an instance of that report", "summary": "Retrieve Report", @@ -13022,7 +13025,7 @@ "/accounts/{accountId}/reports/{reportId}/instances": { "get": { "tags": [ - "/accounts" + "Reports" ], "description": "Retrieve report instances associated with a specific report, including the up-to-date report generation status", "summary": "Retrieve Report Instances", @@ -13062,7 +13065,7 @@ }, "post": { "tags": [ - "/accounts" + "Reports" ], "description": "Create an instance of that report that pulls from data that is filtered by the supplied parameters. Those parameter values must match the parameters that are required as defined by the report, as provided by issuing a GET on the report.\nThe sequence of events is essentially to...\n
  1. issue a GET on the desired report/report-id to retrieve the parameter and other details of the report
  2. issue a POST on the /report/report-id/instances resource, using the parameter information retrieved in the initial call to define the data that is needed
\nThe Location header will provide a link to the created report instance. Note that the report instance itself contains only the metadata describing the instance. A subsequent call to /report/report-id/instances/instance-id/file must be made to actually download the file", "summary": "Create Report Instance", @@ -13130,7 +13133,7 @@ "/accounts/{accountId}/reports/{reportId}/instances/{instanceId}": { "get": { "tags": [ - "/accounts" + "Reports" ], "description": "Retrieve report instance details, including the current report instance status. All of the information required to understand the nature and limits of the reported data are contained in the payload, including the general description information as well as the list of parameters and the values assigned to those parameters", "summary": "Retrieve Report Instance", @@ -13192,7 +13195,7 @@ }, "put": { "tags": [ - "/accounts" + "Reports" ], "description": "Update report instance", "summary": "Update report instance", @@ -13248,7 +13251,7 @@ "/accounts/{accountId}/reports/{reportId}/instances/{instanceId}/file": { "get": { "tags": [ - "/accounts" + "Reports" ], "description": "Download report instance output file, if output is available", "summary": "Download Report Instance File", @@ -13323,7 +13326,7 @@ "/accounts/{accountId}/reports/instances": { "get": { "tags": [ - "/accounts" + "Reports" ], "description": "Retrieve report instances within the account scope, regardless of the report of which the instance is an instance of, including the up-to-date report generation status. This is a convenience API call to make it easier to examine all Instances in scope", "summary": "Retrieve Report Instances on Account", @@ -31198,5 +31201,84 @@ "example": "bf1305b8-8998-1111-2222-51ba3ce52d4e" } } - } + }, + "tags": [ + { + "name": "10DLC" + }, + { + "name": "Addresses" + }, + { + "name": "Applications", + "description": "Bandwidth uses HTTP webhooks to send message & voice events to any publicly addressable url.", + "externalDocs": { + "description": "Application guide", + "url": "/docs/account/applications/" + } + }, + { + "name": "Bulk Port-In", + "description": "Manage bulk port-in orders", + "externalDocs": { + "description": "Bulk port-in guide", + "url": "/docs/numbers/guides/bulkportins/" + } + }, + { + "name": "Callbacks" + }, + { + "name": "Cities" + }, + { + "name": "DLDA", + "description": "DLDA = Directory Listing and Directory Assistance. A DLDA resource associates a TN with a Street Address. This gets updated in a Network Database.", + "externalDocs": { + "description": "DLDA guide", + "url": "/docs/numbers/guides/manageNumberFeatures/#directory-listing-and-directory-assistance-dlda" + } + }, + { + "name": "DLR", + "description": "DLR - Dynamic location routing", + "externalDocs": { + "description": "DLR guide", + "url": "/docs/emergency/dashboard/dlr/" + } + }, + { + "name": "LIDB", + "description": "LIDB - Line Information DataBase", + "externalDocs": { + "description": "LIDB guide", + "url": "/docs/numbers/guides/manageNumberFeatures/#calling-name-display-update-lidb" + } + }, + { + "name": "Rate Centers" + }, + { + "name": "Porting", + "description": "", + "externalDocs": { + "description": "Porting guide", + "url": "/docs/numbers/guides/portingNumbers/" + } + }, + { + "name": "Reports", + "externalDocs": { + "description": "Reports guide", + "url": "/docs/numbers/guides/downloadingReports/" + } + }, + { + "name": "Tns" + }, + { + "name": "/accounts" + } + + ] }