warb 0.1.4 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d0ceb84f9bce4434cb413bee092051e345693d5bfeaa4f4e529e7661eb659f50
-  data.tar.gz: 6ecc6f330c73559e1abd7d17cb817cb894e61fa5055cc1ec5cab9ebd35ff607e
+  metadata.gz: 58ff4cfa4904a9a820c4b5906b947b6f5dcbd3e5a3afa76a9e88ed3f83488bb8
+  data.tar.gz: 1edcbcef65fd5f128cb0cf475f4b5c6ae8e4e285a4b57335b80818e0487f874a
 SHA512:
-  metadata.gz: e7be228f7823f7d9da7aa2820f4ad91f74acf13d31c8e662ab613c8748231e069527258fc7d66333007785541a419fcba26a4a2ae9aa54159b3b6891eb06d8cb
-  data.tar.gz: ba129a442d7afbb050591903c6b753ad4e0c62360c9c2955b640a039a79f5d8dc42a07210d1c279e651920fd49bdc00f3e0a0bd2458426f9c851015ace4b8111
+  metadata.gz: 43cabbb2bcd395dbbc32eacf0f170e00c5fa913f9edbe4543b9b19f81278648ccae955ac64601182fc468ab02ae81cdb81ae1c07d4601f793dd1645cad28a698
+  data.tar.gz: f7ef031988f7c39be607047ebab9e56d627b848527fce0baa5043f1108a93e378e4e7b6d7df853240bcdba9ccb46b0c0c8ba135833fc31fbccaf01175dab9ba6

data/.rubocop.yml

@@ -1,15 +1,8 @@
-plugins:
-  - rubocop-rspec
-
 AllCops:
   TargetRubyVersion: 3.1
-  NewCops: enable
-  SuggestExtensions: false
-  Exclude:
-    - examples/**/*
-    - bin/*
-Style/Documentation:
-  Enabled: false
 
-RSpec/NestedGroups:
-  Enabled: false
+Style/StringLiterals:
+  EnforcedStyle: double_quotes
+
+Style/StringLiteralsInInterpolation:
+  EnforcedStyle: double_quotes

data/README.md

@@ -9,16 +9,18 @@ A Ruby Gem focused on wrap all the functionalities and use cases of the WhatsApp
 
 ## Installation
 
-Add `warb` to your bundle
+TODO: Replace `UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG` with your gem name right after releasing it to RubyGems.org. Please do not do it earlier due to security reasons. Alternatively, replace this section with instructions to install your gem from git if you don't plan to release to RubyGems.org.
 
-```ruby
-bundle add warb
+Install the gem and add to the application's Gemfile by executing:
+
+```bash
+bundle add UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG
 ```
 
-or add it manually to your Gemfile if you prefer.
+If bundler is not being used to manage dependencies, install the gem by executing:
 
-```ruby
-gem 'warb'
+```bash
+gem install UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG
 ```
 
 ## Configuration
@@ -88,26 +90,9 @@ Warb.message.dispatch(recipient_number) do |builder|
 end
 ```
 
-### What types of messages can I send?
-
-Warb implements the main types of WhatsApp messages, you can follow the message types [`here`](docs/messages/README.md#messages-types)
-
-examples:
-
-```ruby
-
-warb = Warb.new(...)
-
-warb.message.dispatch(...)
-warb.audio.dispatch(...)
-warb.video.dispatch(...)
-warb.image.dispatch(...)
-...
-```
-
 ### Find all usage examples
 
-We suggest heading to the [`examples`](examples) directory, where you'll find documentation files with plenty of usage examples, organized by **Resources** (**Resources** are the types of messages you can send via WhatsApp using Warb).
+We suggest heading to the `examples/` directory, where you'll find documentation files with plenty of usage examples, organized by **Resources** (**Resources** are the types of messages you can send via WhatsApp using Warb).
 
 You can also check the [`docs`](docs/README.md) for a more structured overview of the available resources and their usage.
 
@@ -124,14 +109,6 @@ To enable this kind of flow, you’ll need to know **when** a message is receive
 > ⚠️ **Note:** This gem **does not** provide built-in support for webhooks.
 > However, you can look at [`examples/webhook.rb`](examples/webhook.rb) for a starting point on how to implement it. Also, check the [official documentation](https://developers.facebook.com/docs/whatsapp/cloud-api/webhooks/payload-examples) for more details if you get stuck.
 
-## Deploy
-
-```
-git tag v0.0.2
-git push origin main --tags
-```
-
-
 ## Development
 
 After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.

data/Rakefile

@@ -1,11 +1,11 @@
 # frozen_string_literal: true
 
-require 'bundler/gem_tasks'
-require 'rspec/core/rake_task'
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
 
 RSpec::Core::RakeTask.new(:spec)
 
-require 'rubocop/rake_task'
+require "rubocop/rake_task"
 
 RuboCop::RakeTask.new
 

data/docs/README.md

@@ -10,7 +10,4 @@ Refer to [webhook](webhook.md) for more details on how to setup a webhook to get
 Refer to [messages](./messages/README.md) for more details on how to send messages using Warb.
 
 ## Components
-Refer to [components](./components/README.md) for more details on how Warb components work.
-
-## Resources
-Refer to [resources](./resources/README.md) for more details on resources.
+Refer to [components](./components/README.md) for more details on how Warb components work.

data/docs/components/README.md

@@ -18,7 +18,4 @@ Here is a table of available components, and where they can be used:
 | `Warb::Components::ReplyButtonAction` | [Interactive Reply Button](../messages/interactive_reply_button.md)             | [Reply Button Action](./reply_button_action) |
 | `Warb::Components::Row`               | [Interactive List](../messages/interactive_list.md)                             | [Row](./row.md)                              |
 | `Warb::Components::ListAction`        | [Interactive List](../messages/interactive_list.md)                             | [List Action](./list_action.md)              |
-| `Warb::Components::Section`           | [Interactive List](../messages/interactive_list.md)                             | [Section](./section.md)                      |
-| `Warb::Components::Button`            | [Template](../messages/template.md)                                             | [Button](./button.md)                        |
-| `Warb::Components::UrlButton`         | [Template](../messages/template.md)                                             | [UrlButton](./url_button.md)                 |
-| `Warb::Components::CopyCodeButton`    | [Template](../messages/template.md)                                             | [CopyCodeButton](./copy_code_button.md)      |
+| `Warb::Components::Section`           | [Interactive List](../messages/interactive_list.md)                             | [Section](./section.md)                      |

data/docs/messages/README.md

@@ -71,10 +71,9 @@ Messages are sent using a helper dispatcher and its resource class. Here is a li
 | Video                          | `Warb::Resources::Video`                      | `video`                             | [Video Message](./video.md)                                                   |
 | Special Dispatchers                                                                                                                                                                                  |
 | Indicator                      | `Warb::Resources::Indicator`                  | `indicator`                         | [Indicator Message](./indicator.md)                                           |
-| Template                       | `Warb::Resources::Template`                   | `template`                          | [Template Message](./template.md)                                             |
 
 > Simple Dispatcher doesn't offer any additional functionality, they just send messages.
 
 > Media Dispatchers, aside from sending messages, also provide methods to upload and download media files.
 
-> Special Dispatchers are used for specific purposes, such as sending indicators, reactions or templates.
+> Special Dispatchers are used for specific purposes, such as sending indicators or reactions.

data/docs/messages/flow.md

@@ -1,248 +1,12 @@
 # Flow
 
-Flow is a special type of interactive WhatsApp message that provides a "form-like" experience.
-With ```Warb.flow``` you can send static (navigate) or dynamic (data exchange) flows, both in draft and published modes.
+Flow is a special type of message. We can summarize it simply as a form.
 
-Prerequisites (Meta)
-Business Account + Developer Account
-Verified Business to send flows in production WhatsApp (unverified accounts can only test in Meta’s Flow editor)
-For dynamic flows: endpoint + encryption configured in Meta (to handle user responses)
+At this point of writing, this gem only supports sending existing flows, and it can only send flows which are in draft.
 
-### Quick Examples
-
-##### Send a static draft flow:
-```ruby
-Warb.flow.dispatch(recipient_number, flow_id: "0000000000000000", mode: "draft", screen: "INITIAL", body: "Open flow")
-```
-
-##### Send a dynamic draft flow:
-```ruby
-Warb.flow.dispatch(recipient_number,
-  flow_id:     "0000000000000000",
-  mode:        "draft",
-  flow_action: "data_exchange",
-  body:        "Open flow"
-)
-```
-
-##### Send a dynamic published flow with custom header, body, and footer:
-```ruby
-Warb.flow.dispatch(recipient_number) do |flow|
-  flow.flow_id     = "0000000000000000"
-  flow.flow_action = "data_exchange"
-  flow.mode        = "published"
-  flow.body        = "Hello! Please follow the instructions."
-  flow.footer      = "Need help? Reply to this message."
-
-  flow.header = {
-    type: "document",
-    document: {
-      link:     "https://example.com/contract.pdf",
-      filename: "contract.pdf"
-    }
-  }
-
-  flow.flow_cta = "Sign"
-end
-```
-
-### Dispatching Flow Messages
+To send flows, you can do as following:
 ```ruby
-Warb.flow.dispatch(recipient_number, **params, &block)
+Warb.flow.dispatch(recipient_number, flow_id: "flow_id", screen: "screen")
 ```
-##### Parameters
-| Attribute     | Type     | Required                           | Description                                                 |
-| ------------- | -------- | ---------------------------------- | ----------------------------------------------------------- |
-| `flow_id`     | `String` | Yes                                | The ID of the Flow created in Meta.                         |
-| `body`        | `String` | Yes                                | Body text shown in the Flow message.                        |
-| `flow_action` | `String` | No                                 | `"navigate"` (default) or `"data_exchange"`.                |
-| `mode`        | `String` | Yes if `flow mode == 'draft'`      | `"published"` (default) or `"draft"`.                       |
-| `screen`      | `String` | Yes if `flow_action == "navigate"` | Initial screen to navigate to.                              |
-| `flow_cta`    | `String` | No                                 | Label for the button that opens the Flow.                   |
-| `flow_token`  | `String` | No                                 | Token for dynamic flows (encryption/validation).            |
-| `data`        | `Hash`   | No                                 | Prefill data for navigate flows.                            |
-| `header`      | `Hash`   | No                                 | Optional header (see below).                                |
-| `footer`      | `String` | No                                 | Optional footer text.                                       |
-
-### Supported Headers
-
-You must provide exactly one of the following header types:
 
-##### Text
-```ruby
-{ type: "text", text: "Flow title" }
-```
-
-##### Image
-```ruby
-{ type: "image", image: { id: "MEDIA_ID" } }
-# or
-{ type: "image", image: { link: "https://example.com/img.jpg" } }
-```
-
-##### Video
-```ruby
-{ type: "video", video: { id: "MEDIA_ID" } }
-# or
-{ type: "video", video: { link: "https://example.com/video.mp4" } }
-```
-
-##### Document
-```ruby
-{ type: "document", document: { id: "MEDIA_ID" } }
-# or
-{ type: "document", document: { link: "https://example.com/file.pdf", filename: "file.pdf" } }
-```
-
-##### Note:
-
-id must be obtained from a media upload (Warb.image/video/document.upload).
-
-link must be a public URL. For documents, filename is required to determine preview capabilities.
-
-### Modes and Actions
-##### mode
-
-"published" (default): Published flow. Allows customizing header, body, footer, and flow_cta.
-
-"draft": Draft flow. Usable via Meta Flow editor and sometimes on WhatsApp, but some elements (like body text and CTA) may be restricted.
-
-##### flow_action
-
-"navigate" (default) → static flow
-Requires screen, can include initial data:
-```ruby
-Warb.flow.dispatch(recipient_number,
-  flow_id: "0000000000000000",
-  screen:  "INITIAL",
-  body:    "Continue",
-  data:    { prefill: { name: "Alice", email: "alice@example.com" } }
-)
-```
-
-"data_exchange" → dynamic flow
-No flow_action_payload (omitted automatically):
-```ruby
-Warb.flow.dispatch(recipient_number,
-  flow_id:     "0000000000000000",
-  flow_action: "data_exchange",
-  body:        "Fill the form",
-)
-```
-
-### Block Building
-
-You can also build flows using a block:
-```ruby
-Warb.flow.dispatch(recipient_number) do |flow|
-  flow.flow_id     = "0000000000000000"
-  flow.flow_action = "data_exchange"
-  flow.mode        = "published"
-  flow.body        = "We need some information"
-
-  flow.header = { type: "text", text: "Registration" }
-  flow.footer = "Thanks!"
-
-  flow.flow_cta   = "Open"
-end
-```
-
-### Validations
-
-Before sending, the gem enforces:
-
-flow_id is required → raises ArgumentError: flow_id is required
-
-body is required → raises ArgumentError: body is required for flow message
-
-If flow_action == "navigate" then screen is required →
-raises ArgumentError: screen is required for flow_action=navigate
-
-The Meta API may return additional errors (invalid parameters, missing fields, etc.), which are raised as Warb::BadRequest, Warb::RequestError, etc.
-
-Example Scenarios
-1) Static / Draft
-```ruby
-Warb.flow.dispatch(recipient_number,
-  flow_id: "0000000000000000",
-  screen:  "INITIAL",
-  mode:    "draft",
-  body:    "Open flow"
-)
-```
-
-2) Dynamic / Draft
-```ruby
-Warb.flow.dispatch(recipient_number,
-  flow_id:     "0000000000000000",
-  flow_action: "data_exchange",
-  mode:        "draft",
-  body:        "Fill the form"
-)
-```
-
-3) Dynamic / Published with Document Header
-```ruby
-Warb.flow.dispatch(recipient_number) do |flow|
-  flow.flow_id     = "0000000000000000"
-  flow.flow_action = "data_exchange"
-  flow.mode        = "published"
-  flow.body        = "Please review and sign the document."
-  flow.footer      = "Reply if you need assistance."
-  flow.flow_cta    = "Sign"
-
-  flow.header = {
-    type: "document",
-    document: {
-      link:     "https://www.thecampusqdl.com/uploads/files/pdf_sample_2.pdf",
-      filename: "pdf_sample_2.pdf"
-    }
-  }
-end
-```
-
-4) Static / Published with Image Header (id) and Prefill Data
-```ruby
-image_id = Warb.image.upload(file_path: "banner.jpg", file_type: "image/jpeg")
-
-Warb.flow.dispatch(recipient_number) do |flow|
-  flow.flow_id = "0000000000000000"
-  flow.mode    = "published"
-  flow.body    = "Open and check your data"
-
-  flow.header = { type: "image", image: { id: image_id } }
-
-  flow.screen = "INITIAL"
-  flow.data   = { prefill: { name: "John", email: "john@example.com" } }
-end
-```
-
-### Generated Payload (Reference)
-
-Example payload produced by the gem:
-```ruby
-{
-  "type": "interactive",
-  "interactive": {
-    "type": "flow",
-    "header": { ... },
-    "body": { "text": "..." },
-    "footer": { "text": "..." },
-    "action": {
-      "name": "flow",
-      "parameters": {
-        "flow_message_version": "3",
-        "flow_id": "....",
-        "flow_action": "navigate" | "data_exchange",
-        "mode": "published" | "draft",
-        "flow_cta": "Open",
-        "flow_token": "TOKEN",
-        "flow_action_payload": {
-          "screen": "INITIAL",
-          "data": { "prefill": { ... } }
-        }
-      }
-    }
-  }
-}
-```
+`flow_id` must be the ID of the flow and `screen` must be the ID of the first screen of the flow.

data/docs/messages/interactive_call_to_action_url.md

@@ -28,7 +28,7 @@ Warb.interactive_call_to_action_url.dispatch(recipient_number) do |message|
   message.footer = "footer"
 
   # for header, there's a helper method to create a text header
-  message.add_text_header("Check this out!")
+  message.set_text_header("Check this out!")
 
   # and for action, you can use the build_action method to create a CTA action`
   message.build_action(button_text: "Click Here") do |action|
@@ -37,7 +37,7 @@ Warb.interactive_call_to_action_url.dispatch(recipient_number) do |message|
 end
 ```
 
-Aside from the text header, you can also set an image, video, or document as header using the respective methods, `add_image_header`, `add_video_header`, and `add_document_header`.
+Aside from the text header, you can also set an image, video, or document as header using the respective methods, `set_image_header`, `set_video_header`, and `set_document_header`.
 
 Here is an example of using an image as header:
 
@@ -47,7 +47,7 @@ Warb.interactive_call_to_action_url.dispatch(recipient_number) do |message|
   message.footer = "footer"
 
   # set an image as header
-  message.add_image_header(link: "https://example.com/image.jpg")
+  message.set_image_header(link: "https://example.com/image.jpg")
 
   # the build_action method also returns the built action
   action = message.build_action do |action|
@@ -68,7 +68,7 @@ Warb.interactive_call_to_action_url.dispatch(recipient_number) do |message|
 
   # set a document as header
   # for documents, you can also pass a filename. its extension will be used to determine the MIME type
-  message.add_document_header(link: "https://example.com/document.pdf", filename: "document.pdf")
+  message.set_document_header(link: "https://example.com/document.pdf", filename: "document.pdf")
 
   message.build_action(url: "https://example.com", button_text: "Click here")
 end
@@ -86,11 +86,11 @@ Here is a summary of the fields you can set in the `dispatch` method of the `int
 For header, as seen above, you can set it using the following instance methods:
 | Method                | Named Parameters   | Positional Parameters  | Respective Resource Class   |
 |-----------------------|--------------------|------------------------|-----------------------------|
-| `add_text_header`     | -                  | the content header     | `Warb::Resources::Text`     |
-| `add_image_header`    | `link`             | -                      | `Warb::Resources::Image`    |
-| `add_video_header`    | `link`             | -                      | `Warb::Resources::Video`    |
-| `add_document_header` | `link`, `filename` | -                      | `Warb::Resources::Document` |
+| `set_text_header`     | -                  | the content header     | `Warb::Resources::Text`     |
+| `set_image_header`    | `link`             | -                      | `Warb::Resources::Image`    |
+| `set_video_header`    | `link`             | -                      | `Warb::Resources::Video`    |
+| `set_document_header` | `link`, `filename` | -                      | `Warb::Resources::Document` |
 
 Under the hood, the set header methods will create the respective resource object and call its `build_header` method to prepare the header for sending.
 
-For the action, the `build_action` instance method will create a `Warb::Components::CTAAction` and return it
+For the action, the `build_action` instance method will create a `Warb::Components::CTAAction` and return it

data/docs/messages/interactive_list.md

@@ -77,7 +77,7 @@ Warb.interactive_list.dispatch(recipient_number) do |message|
   message.body = "Choose your preferred language"
   message.footer = "You can change it later"
 
-  message.add_text_header("Language Selection")
+  message.set_text_header("Language Selection")
 
   message.build_action(button_text: "Select") do |action|
     section = action.add_section(title: nil)
@@ -108,7 +108,7 @@ Warb.interactive_list.dispatch(recipient_number) do |message|
   message.body = "Choose your preferred language"
   message.footer = "You can change it later"
 
-  message.add_text_header("Language Selection")
+  message.set_text_header("Language Selection")
 
   message.build_action(button_text: "Select") do |action|
     action.add_section(title: "American Languages") do |american_section|

data/docs/messages/interactive_reply_button.md

@@ -23,7 +23,7 @@ Or you can use the block building strategy to simplify the process:
 
 ```ruby
 Warb.interactive_reply_button.dispatch(recipient_number) do |message|
-  message.add_image_header(media_id: "1341834336894773")
+  message.set_image_header(media_id: "1341834336894773")
 
   message.body = "Select a Language:"
   message.footer = nil
@@ -38,23 +38,23 @@ or you can build the action with the buttons texts directly, passing them to the
 
 ```ruby
 Warb.interactive_reply_button.dispatch(recipient_number, action: action) do |message|
-  message.add_text_header(content: "Options")
+  message.set_text_header(content: "Options")
   message.body = "Select a Language:"
   message.footer = nil
   message.build_action(buttons_texts: ["Português", "English", "Español"])
 end
 ```
 
-Aside from text and image headers, you can also set a video or document as header using the respective methods, `add_video_header` and `add_document_header`.
+Aside from text and image headers, you can also set a video or document as header using the respective methods, `set_video_header` and `set_document_header`.
 
-For text header, `add_text_header` receives a string, while for image, video, and document headers, you can pass a `media_id` or a `link` to the media file.
+For text header, `set_text_header` receives a string, while for image, video, and document headers, you can pass a `media_id` or a `link` to the media file.
 For header, as seen above, you can set it using the following instance methods:
 | Method                | Named Parameters               | Positional Parameters  | Respective Resource Class   |
 |-----------------------|--------------------------------|------------------------|-----------------------------|
-| `add_text_header`     | -                              | the content header     | `Warb::Resources::Text`     |
-| `add_image_header`    | `link`, `media_id`             | -                      | `Warb::Resources::Image`    |
-| `add_video_header`    | `link`, `media_id`             | -                      | `Warb::Resources::Video`    |
-| `add_document_header` | `link`, `media_id`, `filename` | -                      | `Warb::Resources::Document` |
+| `set_text_header`     | -                              | the content header     | `Warb::Resources::Text`     |
+| `set_image_header`    | `link`, `media_id`             | -                      | `Warb::Resources::Image`    |
+| `set_video_header`    | `link`, `media_id`             | -                      | `Warb::Resources::Video`    |
+| `set_document_header` | `link`, `media_id`, `filename` | -                      | `Warb::Resources::Document` |
 
 Either `link` or `media_id` can be used, but not both at the same time.
 
@@ -64,4 +64,4 @@ If you're using a `media_id`, it must be obtained from a previous upload using t
 
 The `filename` for the document header is optional, but if provided, it will be used to determine the MIME type of the document.
 
-For the `action` of the message, you can use the [`Warb::Components::ReplyButtonAction`](../components/reply_button_action.md) class to build the action with the buttons texts.
+For the `action` of the message, you can use the [`Warb::Components::ReplyButtonAction`](../components/reply_button_action.md) class to build the action with the buttons texts.

data/docs/setup.md

@@ -43,48 +43,4 @@ Warb.setup do |config|
 end
 ```
 
-Also, note that calling `Warb.setup` multiple times **WILL NOT** override the previous configuration, so you can use it to change the global configuration at any time.
-
-## Phone numbers (quality monitoring)
-
-You can fetch all phone numbers attached to your WhatsApp Business Account (WABA) and their quality/operational signals.
-
-Requirements: make sure you have configured a business_id in your global setup (this method uses the business context, not the sender/phone context).
-```ruby
-Warb.setup do |config|
-  config.access_token = "ACCESS_TOKEN"
-  config.business_id  = "BUSINESS_ID"      # <-- required here
-  config.sender_id    = "SENDER_ID"    # still used for message dispatch
-end
-```
-
-#### Global usage
-```ruby
-phones = Warb.list_phone_numbers
-```
-
-#### Sample response (unwrapped data array):
-```ruby
-=> [
-  {
-    "verified_name"            => "Test",
-    "code_verification_status" => "NOT_VERIFIED",
-    "display_phone_number"     => "00000000000",
-    "quality_rating"           => "GREEN",
-    "platform_type"            => "CLOUD_API",
-    "throughput"               => { "level" => "STANDARD" },
-    "webhook_configuration"    => { "application" => "https://example.com/" },
-    "id"                       => "(phone_number_id)"
-  }
-]
-```
-
-#### Notes
-
-This method returns the data array directly. If you need paging cursors, call the raw client:
-```ruby
-raw = Warb.client.get("phone_numbers", {}, endpoint_prefix: :business_id)
-raw.body # => { "data" => [...], "paging" => { "cursors" => {...} } }
-```
-
-Non-2xx responses raise Warb::RequestError (or subclasses), so you can rescue them in your app.
+Also, note that calling `Warb.setup` multiple times **WILL NOT** override the previous configuration, so you can use it to change the global configuration at any time.

data/examples/audio.rb

@@ -1,15 +1,15 @@
 # frozen_string_literal: true
 
-require_relative '../lib/warb'
+require_relative "../lib/warb"
 
 # Configure your variables here
 
-access_token = ''
-business_id = ''
-sender_id = ''
-recipient_number = ''
+access_token = ""
+business_id = ""
+sender_id = ""
+recipient_number = ""
 
-audio_link = ''
+audio_link = ""
 
 # We recommend testing one section at a time, as it can be overwhelming to see all the messages at once.
 # So you can comment out the sections you don't want to test.
@@ -25,8 +25,8 @@ warb_from_setup = Warb.setup do |config|
 end
 
 # To send audio using its ID, you may need to retrieve it first, which can be retrieved this way
-file_path = '' # fill this in with the file path pointing to wherever the audio is located
-file_type = '' # fill this in with the mimetype of the audio to be uploaded
+file_path = "" # fill this in with the file path pointing to wherever the audio is located
+file_type = "" # fill this in with the mimetype of the audio to be uploaded
 # allow values for file_type: audio/aac, audio/amr, audio/mpeg, audio/mp4 or audio/ogg
 audio_id = warb_from_setup.audio.upload(file_path: file_path, file_type: file_type)
 # if you already have an audio id, you can simply replace the above line with such id
@@ -53,8 +53,8 @@ warb_from_new = Warb.new(
 )
 
 # Same as stated above, if you need an audio id, you can upload it this way
-file_path = '' # fill this in with the file path pointing to wherever the audio is located
-file_type = '' # fill this in with the mimetype of the audio to be uploaded
+file_path = "" # fill this in with the file path pointing to wherever the audio is located
+file_type = "" # fill this in with the mimetype of the audio to be uploaded
 # allow values for file_type: audio/aac, audio/amr, audio/mpeg, audio/mp4 or audio/ogg
 audio_id = warb_from_setup.audio.upload(file_path: file_path, file_type: file_type)
 # if you already have an audio id, you can simply replace the above line with such id