telnyx-10dlc-ruby

<!-- Auto-generated from Telnyx OpenAPI specs. Do not edit. --> # Telnyx 10DLC - Ruby ## Installation ```bash gem install telnyx ``` ## Setup ```ruby require "telnyx" client = Telnyx::Client.new( api_key: ENV["TELNYX_API_KEY"], # This is the default and can be omitted ) ``` All examples below assume `client` is already initialized as shown above. ## Error Handling All API calls can fail with network errors, rate limits (429), validation errors (422), or authentication errors (401). Always handle errors in production code: ```ruby telnyx_brand = client.messaging_10dlc.brand.create( country: "US", display_name: "ABC Mobile", email: "support@example.com", entity_type: :PRIVATE_PROFIT, vertical: :TECHNOLOGY ) puts(telnyx_brand) ``` Common error codes: `401` invalid API key, `403` insufficient permissions, `404` resource not found, `422` validation error (check field formats), `429` rate limited (retry with exponential backoff). ## Important Notes - **Pagination:** Use `.auto_paging_each` for automatic iteration: `page.auto_paging_each { |item| puts item.id }`. ## Operational Caveats - 10DLC is sequential: create the brand first, then submit the campaign, then attach messaging infrastructure such as the messaging profile. - Registration calls are not enough by themselves. Messaging cannot use the campaign until the assignment step completes successfully. - Treat registration status fields as part of the control flow. Do not assume the campaign is send-re...