You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you provided your Environment information? - Doesn't apply here
Have you provided a sample code snippet?
Have you provided a stack trace? - Doesn't apply here
Have you outlined the expected behavior?
Description
The issue arises from a discrepancy in the Bandwidth Iris SDK documentation. When creating an LIDB order, the documentation provides the following structure:
data={:customer_order_id=>"A test order",:lidb_tn_groups=>{:lidb_tn_group=>{:telephone_numbers=>["8048030097","8045030098"],# this is the issue:subscriber_information=>"Joes Grarage",# typo here:use_type=>"RESIDENTIAL",:visibility=>"PUBLIC"}}}BandwidthIris::Lidb.create(data)
However, this structure generates the following XML:
StatusCode: 400Reason:
HTTPHeaders: { ... }ResponseBody: {:response_status=>{:error_code=>1003,:description=>"TelephoneNumbers is required"}}
The problem seems to be that the documentation incorrectly suggests using a plain array for telephone numbers, which leads to the SDK generating invalid XML. Additionally, there's a typo in the subscriber_information field ("Joes Grarage" instead of "Joes Garage").
Checklist
Description
The issue arises from a discrepancy in the Bandwidth Iris SDK documentation. When creating an LIDB order, the documentation provides the following structure:
However, this structure generates the following XML:
This results in a Bad Request error:
The problem seems to be that the documentation incorrectly suggests using a plain array for telephone numbers, which leads to the SDK generating invalid XML. Additionally, there's a typo in the subscriber_information field ("Joes Grarage" instead of "Joes Garage").
Link to the documentation: https://github.com/Bandwidth/ruby-bandwidth-iris?tab=readme-ov-file#create
Expected Behavior
Creates a valid LIDB order XML according to the Bandwidth documentation website: https://dev.bandwidth.com/docs/numbers/guides/manageNumberFeatures/#calling-name-display-update-lidb
Suggested Fix
After testing in my application, the following structure works correctly:
The text was updated successfully, but these errors were encountered: