mailslurp_client 7.0.8 → 7.2.4

data/spec/api/domain_controller_api_spec.rb

@@ -1,82 +0,0 @@
-=begin
-#MailSlurp API
-
-#MailSlurp is an API for sending and receiving emails from dynamically allocated email addresses. It's designed for developers and QA teams to test applications, process inbound emails, send templated notifications, attachments, and more.   ## Resources - [Homepage](https://www.mailslurp.com) - Get an [API KEY](https://app.mailslurp.com/sign-up/) - Generated [SDK Clients](https://www.mailslurp.com/docs/) - [Examples](https://github.com/mailslurp/examples) repository  ## Basic Concepts  ### Inboxes  Inboxes have real email addresses that can send and receive emails. You can create inboxes with specific email addresses (using custom domains). You can also use randomly assigned MailSlurp addresses as unique, disposable test addresses.   See the InboxController or [inbox and email address guide](https://www.mailslurp.com/guides/) for more information.  ### Receive Emails You can receive emails in a number of ways. You can fetch emails and attachments directly from an inbox. Or you can use `waitFor` endpoints to hold a connection open until an email is received that matches given criteria (such as subject or body content). You can also use webhooks to have emails from multiple inboxes forwarded to your server via HTTP POST.  InboxController methods with `waitFor` in the name have a long timeout period and instruct MailSlurp to wait until an expected email is received. You can set conditions on email counts, subject or body matches, and more.  Most receive methods only return an email ID and not the full email (to keep response sizes low). To fetch the full body or attachments for an email use the email's ID with EmailController endpoints.  See the InboxController or [receiving emails guide](https://www.mailslurp.com/guides/) for more information.  ### Send Emails You can send templated HTML emails in several ways. You must first create an inbox to send an email. An inbox can have a specific address or a randomly assigned one. You can send emails from an inbox using `to`, `cc`, and `bcc` recipient lists or with contacts and contact groups.   Emails can contain plain-text or HTML bodies. You can also use email templates that support [moustache](https://mustache.github.io/) template variables. You can send attachments by first posting files to the AttachmentController and then using the returned IDs in the `attachments` field of the send options.  See the InboxController or [sending emails guide](https://www.mailslurp.com/guides/) for more information.  ### Templates MailSlurp emails support templates. You can create templates in the dashboard or API that contain [moustache](https://mustache.github.io/) style variables: for instance `Hello {{name}}`. Then when sending emails you can pass a map of variables names and values to be used. Additionally, when sending emails with contact groups you can use properties of the contact in your templates like `{{firstName}}` and `{{lastName}}`.  > You can do a lot more with MailSlurp so see the included documentation for more information.  
-
-The version of the OpenAPI document: 6.5.2
-
-Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 4.2.3
-
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for MailSlurpClient::DomainControllerApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'DomainControllerApi' do
-  before do
-    # run before each test
-    @api_instance = MailSlurpClient::DomainControllerApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of DomainControllerApi' do
-    it 'should create an instance of DomainControllerApi' do
-      expect(@api_instance).to be_instance_of(MailSlurpClient::DomainControllerApi)
-    end
-  end
-
-  # unit tests for create_domain
-  # Create Domain
-  # Link a domain that you own with MailSlurp so you can create email addresses using it. Endpoint returns DNS records used for validation. You must add these verification records to your host provider's DNS setup to verify the domain.
-  # @param domain_options domainOptions
-  # @param [Hash] opts the optional parameters
-  # @return [DomainDto]
-  describe 'create_domain test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for delete_domain
-  # Delete a domain
-  # Delete a domain. This will disable any existing inboxes that use this domain.
-  # @param id id
-  # @param [Hash] opts the optional parameters
-  # @return [nil]
-  describe 'delete_domain test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_domain
-  # Get a domain
-  # Returns domain verification status and tokens for a given domain
-  # @param id id
-  # @param [Hash] opts the optional parameters
-  # @return [DomainDto]
-  describe 'get_domain test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_domains
-  # Get domains
-  # List all custom domains you have created
-  # @param [Hash] opts the optional parameters
-  # @return [Array<DomainPreview>]
-  describe 'get_domains test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end

data/spec/api/email_controller_api_spec.rb

@@ -1,162 +0,0 @@
-=begin
-#MailSlurp API
-
-#MailSlurp is an API for sending and receiving emails from dynamically allocated email addresses. It's designed for developers and QA teams to test applications, process inbound emails, send templated notifications, attachments, and more.   ## Resources - [Homepage](https://www.mailslurp.com) - Get an [API KEY](https://app.mailslurp.com/sign-up/) - Generated [SDK Clients](https://www.mailslurp.com/docs/) - [Examples](https://github.com/mailslurp/examples) repository  ## Basic Concepts  ### Inboxes  Inboxes have real email addresses that can send and receive emails. You can create inboxes with specific email addresses (using custom domains). You can also use randomly assigned MailSlurp addresses as unique, disposable test addresses.   See the InboxController or [inbox and email address guide](https://www.mailslurp.com/guides/) for more information.  ### Receive Emails You can receive emails in a number of ways. You can fetch emails and attachments directly from an inbox. Or you can use `waitFor` endpoints to hold a connection open until an email is received that matches given criteria (such as subject or body content). You can also use webhooks to have emails from multiple inboxes forwarded to your server via HTTP POST.  InboxController methods with `waitFor` in the name have a long timeout period and instruct MailSlurp to wait until an expected email is received. You can set conditions on email counts, subject or body matches, and more.  Most receive methods only return an email ID and not the full email (to keep response sizes low). To fetch the full body or attachments for an email use the email's ID with EmailController endpoints.  See the InboxController or [receiving emails guide](https://www.mailslurp.com/guides/) for more information.  ### Send Emails You can send templated HTML emails in several ways. You must first create an inbox to send an email. An inbox can have a specific address or a randomly assigned one. You can send emails from an inbox using `to`, `cc`, and `bcc` recipient lists or with contacts and contact groups.   Emails can contain plain-text or HTML bodies. You can also use email templates that support [moustache](https://mustache.github.io/) template variables. You can send attachments by first posting files to the AttachmentController and then using the returned IDs in the `attachments` field of the send options.  See the InboxController or [sending emails guide](https://www.mailslurp.com/guides/) for more information.  ### Templates MailSlurp emails support templates. You can create templates in the dashboard or API that contain [moustache](https://mustache.github.io/) style variables: for instance `Hello {{name}}`. Then when sending emails you can pass a map of variables names and values to be used. Additionally, when sending emails with contact groups you can use properties of the contact in your templates like `{{firstName}}` and `{{lastName}}`.  > You can do a lot more with MailSlurp so see the included documentation for more information.  
-
-The version of the OpenAPI document: 6.5.2
-
-Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 4.2.3
-
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for MailSlurpClient::EmailControllerApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'EmailControllerApi' do
-  before do
-    # run before each test
-    @api_instance = MailSlurpClient::EmailControllerApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of EmailControllerApi' do
-    it 'should create an instance of EmailControllerApi' do
-      expect(@api_instance).to be_instance_of(MailSlurpClient::EmailControllerApi)
-    end
-  end
-
-  # unit tests for delete_all_emails
-  # Delete all emails
-  # Deletes all emails
-  # @param [Hash] opts the optional parameters
-  # @return [nil]
-  describe 'delete_all_emails test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for delete_email
-  # Delete Email
-  # Deletes an email and removes it from the inbox
-  # @param email_id emailId
-  # @param [Hash] opts the optional parameters
-  # @return [nil]
-  describe 'delete_email test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for download_attachment
-  # Get email attachment
-  # Returns the specified attachment for a given email as a byte stream (file download). Get the attachmentId from the email response.
-  # @param attachment_id attachmentId
-  # @param email_id emailId
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :api_key Can pass apiKey in url for this request if you wish to download the file in a browser
-  # @return [String]
-  describe 'download_attachment test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for forward_email
-  # Forward Email
-  # Forward email content to given recipients
-  # @param email_id emailId
-  # @param forward_email_options forwardEmailOptions
-  # @param [Hash] opts the optional parameters
-  # @return [nil]
-  describe 'forward_email test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_attachment_meta_data
-  # Get email attachment metadata
-  # Returns the metadata such as name and content-type for a given attachment and email.
-  # @param attachment_id attachmentId
-  # @param email_id emailId
-  # @param [Hash] opts the optional parameters
-  # @return [AttachmentMetaData]
-  describe 'get_attachment_meta_data test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_attachments
-  # Get all email attachment metadata
-  # Returns an array of attachment metadata such as name and content-type for a given email if present.
-  # @param email_id emailId
-  # @param [Hash] opts the optional parameters
-  # @return [Array<AttachmentMetaData>]
-  describe 'get_attachments test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_email
-  # Get Email Content
-  # Returns a email summary object with headers and content. To retrieve the raw unparsed email use the getRawMessage endpoint
-  # @param email_id emailId
-  # @param [Hash] opts the optional parameters
-  # @return [Email]
-  describe 'get_email test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_emails_paginated
-  # Get all emails
-  # Responses are paginated
-  # @param [Hash] opts the optional parameters
-  # @option opts [Array<String>] :inbox_id Optional inbox ids to filter by. Can be repeated
-  # @option opts [Integer] :page Optional page index in email list pagination
-  # @option opts [Integer] :size Optional page size in email list pagination
-  # @option opts [String] :sort Optional createdAt sort direction ASC or DESC
-  # @option opts [Boolean] :unread_only Optional filter for unread emails only
-  # @return [PageEmailProjection]
-  describe 'get_emails_paginated test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_raw_email_contents
-  # Get Raw Email Content
-  # Returns a raw, unparsed and unprocessed email
-  # @param email_id emailId
-  # @param [Hash] opts the optional parameters
-  # @return [String]
-  describe 'get_raw_email_contents test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for validate_email
-  # Validate email
-  # Validate HTML content of email
-  # @param email_id emailId
-  # @param [Hash] opts the optional parameters
-  # @return [ValidationDto]
-  describe 'validate_email test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end

data/spec/api/form_controller_api_spec.rb

@@ -1,54 +0,0 @@
-=begin
-#MailSlurp API
-
-#MailSlurp is an API for sending and receiving emails from dynamically allocated email addresses. It's designed for developers and QA teams to test applications, process inbound emails, send templated notifications, attachments, and more.   ## Resources - [Homepage](https://www.mailslurp.com) - Get an [API KEY](https://app.mailslurp.com/sign-up/) - Generated [SDK Clients](https://www.mailslurp.com/docs/) - [Examples](https://github.com/mailslurp/examples) repository 
-
-The version of the OpenAPI document: d1659dc1567a5b62f65d0612107a50aace03e085
-
-Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 4.2.3
-
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for MailSlurpClient::FormControllerApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'FormControllerApi' do
-  before do
-    # run before each test
-    @api_instance = MailSlurpClient::FormControllerApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of FormControllerApi' do
-    it 'should create an instance of FormControllerApi' do
-      expect(@api_instance).to be_instance_of(MailSlurpClient::FormControllerApi)
-    end
-  end
-
-  # unit tests for submit_form
-  # Submit a form to be parsed and sent as an email to an address determined by the form fields
-  # This endpoint allows you to submit HTML forms and receive the field values and files via email.   #### Parameters The endpoint looks for special meta parameters in the form fields OR in the URL request parameters. The meta parameters can be used to specify the behaviour of the email.   You must provide at-least a `_to` email address or a `_toAlias` email alias ID to tell the endpoint where the form should be emailed. These can be submitted as hidden HTML input fields with the corresponding `name` attributes or as URL query parameters such as `?_to=test@example.com`  The endpoint takes all other form fields that are named and includes them in the message body of the email. Files are sent as attachments.  #### Submitting This endpoint accepts form submission via POST method. It accepts `application/x-www-form-urlencoded`, and `multipart/form-data` content-types.  #### HTML Example ```html <form    action=\"https://api.mailslurp.com/forms\"   method=\"post\" >   <input name=\"_to\" type=\"hidden\" value=\"test@example.com\"/>   <textarea name=\"feedback\"></textarea>   <button type=\"submit\">Submit</button> </form> ```  #### URL Example ```html <form    action=\"https://api.mailslurp.com/forms?_toAlias=test@example.com\"   method=\"post\" >   <textarea name=\"feedback\"></textarea>   <button type=\"submit\">Submit</button> </form> ```    The email address is specified by a `_to` field OR is extracted from an email alias specified by a `_toAlias` field (see the alias controller for more information).  Endpoint accepts .  You can specify a content type in HTML forms using the `enctype` attribute, for instance: `<form enctype=\"multipart/form-data\">`.  
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :_email_address Email address of the submitting user. Include this if you wish to record the submitters email address and reply to it later.
-  # @option opts [String] :_redirect_to Optional URL to redirect form submitter to after submission. If not present user will see a success message.
-  # @option opts [String] :_spam_check Optional but recommended field that catches spammers out. Include as a hidden form field but LEAVE EMPTY. Spam-bots will usually fill every field. If the _spamCheck field is filled the form submission will be ignored.
-  # @option opts [String] :_subject Optional subject of the email that will be sent.
-  # @option opts [String] :_success_message Optional success message to display if no _redirectTo present.
-  # @option opts [String] :_to The email address that submitted form should be sent to. Either this or _toAlias must be present for a form to be successfully submitted..
-  # @option opts [String] :_to_alias ID of an email alias to that form should be sent to. Aliases must be created before submission and can be used to hide an email address and reduce spam.
-  # @option opts [String] :other_parameters All other parameters or fields will be accepted and attached to the sent email. This includes files and any HTML form field with a name. These fields will become the body of the email that is sent.
-  # @return [String]
-  describe 'submit_form test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end

data/spec/api/group_controller_api_spec.rb

@@ -1,126 +0,0 @@
-=begin
-#MailSlurp API
-
-#MailSlurp is an API for sending and receiving emails from dynamically allocated email addresses. It's designed for developers and QA teams to test applications, process inbound emails, send templated notifications, attachments, and more.   ## Resources - [Homepage](https://www.mailslurp.com) - Get an [API KEY](https://app.mailslurp.com/sign-up/) - Generated [SDK Clients](https://www.mailslurp.com/docs/) - [Examples](https://github.com/mailslurp/examples) repository  ## Basic Concepts  ### Inboxes  Inboxes have real email addresses that can send and receive emails. You can create inboxes with specific email addresses (using custom domains). You can also use randomly assigned MailSlurp addresses as unique, disposable test addresses.   See the InboxController or [inbox and email address guide](https://www.mailslurp.com/guides/) for more information.  ### Receive Emails You can receive emails in a number of ways. You can fetch emails and attachments directly from an inbox. Or you can use `waitFor` endpoints to hold a connection open until an email is received that matches given criteria (such as subject or body content). You can also use webhooks to have emails from multiple inboxes forwarded to your server via HTTP POST.  InboxController methods with `waitFor` in the name have a long timeout period and instruct MailSlurp to wait until an expected email is received. You can set conditions on email counts, subject or body matches, and more.  Most receive methods only return an email ID and not the full email (to keep response sizes low). To fetch the full body or attachments for an email use the email's ID with EmailController endpoints.  See the InboxController or [receiving emails guide](https://www.mailslurp.com/guides/) for more information.  ### Send Emails You can send templated HTML emails in several ways. You must first create an inbox to send an email. An inbox can have a specific address or a randomly assigned one. You can send emails from an inbox using `to`, `cc`, and `bcc` recipient lists or with contacts and contact groups.   Emails can contain plain-text or HTML bodies. You can also use email templates that support [moustache](https://mustache.github.io/) template variables. You can send attachments by first posting files to the AttachmentController and then using the returned IDs in the `attachments` field of the send options.  See the InboxController or [sending emails guide](https://www.mailslurp.com/guides/) for more information.  ### Templates MailSlurp emails support templates. You can create templates in the dashboard or API that contain [moustache](https://mustache.github.io/) style variables: for instance `Hello {{name}}`. Then when sending emails you can pass a map of variables names and values to be used. Additionally, when sending emails with contact groups you can use properties of the contact in your templates like `{{firstName}}` and `{{lastName}}`.  > You can do a lot more with MailSlurp so see the included documentation for more information.  
-
-The version of the OpenAPI document: 6.5.2
-
-Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 4.2.3
-
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for MailSlurpClient::GroupControllerApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'GroupControllerApi' do
-  before do
-    # run before each test
-    @api_instance = MailSlurpClient::GroupControllerApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of GroupControllerApi' do
-    it 'should create an instance of GroupControllerApi' do
-      expect(@api_instance).to be_instance_of(MailSlurpClient::GroupControllerApi)
-    end
-  end
-
-  # unit tests for add_contacts_to_group
-  # Add contacts to a group
-  # @param group_id groupId
-  # @param update_group_contacts_option updateGroupContactsOption
-  # @param [Hash] opts the optional parameters
-  # @return [GroupContactsDto]
-  describe 'add_contacts_to_group test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for create_group
-  # Create a group
-  # @param create_group_options createGroupOptions
-  # @param [Hash] opts the optional parameters
-  # @return [GroupDto]
-  describe 'create_group test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for delete_group
-  # Delete group
-  # @param group_id groupId
-  # @param [Hash] opts the optional parameters
-  # @return [nil]
-  describe 'delete_group test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_all_groups
-  # Get all Contact Groups in paginated format
-  # @param [Hash] opts the optional parameters
-  # @option opts [Integer] :page Optional page index in inbox list pagination
-  # @option opts [Integer] :size Optional page size in inbox list pagination
-  # @option opts [String] :sort Optional createdAt sort direction ASC or DESC
-  # @return [PageGroupProjection]
-  describe 'get_all_groups test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_group
-  # Get group
-  # @param group_id groupId
-  # @param [Hash] opts the optional parameters
-  # @return [GroupDto]
-  describe 'get_group test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_group_with_contacts
-  # Get group and contacts belonging to it
-  # @param group_id groupId
-  # @param [Hash] opts the optional parameters
-  # @return [GroupContactsDto]
-  describe 'get_group_with_contacts test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_groups
-  # Get all groups
-  # @param [Hash] opts the optional parameters
-  # @return [Array<GroupProjection>]
-  describe 'get_groups test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for remove_contacts_from_group
-  # Remove contacts from a group
-  # @param group_id groupId
-  # @param update_group_contacts_option updateGroupContactsOption
-  # @param [Hash] opts the optional parameters
-  # @return [GroupContactsDto]
-  describe 'remove_contacts_from_group test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end

data/spec/api/inbox_controller_api_spec.rb

@@ -1,172 +0,0 @@
-=begin
-#MailSlurp API
-
-#MailSlurp is an API for sending and receiving emails from dynamically allocated email addresses. It's designed for developers and QA teams to test applications, process inbound emails, send templated notifications, attachments, and more.   ## Resources - [Homepage](https://www.mailslurp.com) - Get an [API KEY](https://app.mailslurp.com/sign-up/) - Generated [SDK Clients](https://www.mailslurp.com/docs/) - [Examples](https://github.com/mailslurp/examples) repository  ## Basic Concepts  ### Inboxes  Inboxes have real email addresses that can send and receive emails. You can create inboxes with specific email addresses (using custom domains). You can also use randomly assigned MailSlurp addresses as unique, disposable test addresses.   See the InboxController or [inbox and email address guide](https://www.mailslurp.com/guides/) for more information.  ### Receive Emails You can receive emails in a number of ways. You can fetch emails and attachments directly from an inbox. Or you can use `waitFor` endpoints to hold a connection open until an email is received that matches given criteria (such as subject or body content). You can also use webhooks to have emails from multiple inboxes forwarded to your server via HTTP POST.  InboxController methods with `waitFor` in the name have a long timeout period and instruct MailSlurp to wait until an expected email is received. You can set conditions on email counts, subject or body matches, and more.  Most receive methods only return an email ID and not the full email (to keep response sizes low). To fetch the full body or attachments for an email use the email's ID with EmailController endpoints.  See the InboxController or [receiving emails guide](https://www.mailslurp.com/guides/) for more information.  ### Send Emails You can send templated HTML emails in several ways. You must first create an inbox to send an email. An inbox can have a specific address or a randomly assigned one. You can send emails from an inbox using `to`, `cc`, and `bcc` recipient lists or with contacts and contact groups.   Emails can contain plain-text or HTML bodies. You can also use email templates that support [moustache](https://mustache.github.io/) template variables. You can send attachments by first posting files to the AttachmentController and then using the returned IDs in the `attachments` field of the send options.  See the InboxController or [sending emails guide](https://www.mailslurp.com/guides/) for more information.  ### Templates MailSlurp emails support templates. You can create templates in the dashboard or API that contain [moustache](https://mustache.github.io/) style variables: for instance `Hello {{name}}`. Then when sending emails you can pass a map of variables names and values to be used. Additionally, when sending emails with contact groups you can use properties of the contact in your templates like `{{firstName}}` and `{{lastName}}`.  > You can do a lot more with MailSlurp so see the included documentation for more information.  
-
-The version of the OpenAPI document: 6.5.2
-
-Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 4.2.3
-
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for MailSlurpClient::InboxControllerApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'InboxControllerApi' do
-  before do
-    # run before each test
-    @api_instance = MailSlurpClient::InboxControllerApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of InboxControllerApi' do
-    it 'should create an instance of InboxControllerApi' do
-      expect(@api_instance).to be_instance_of(MailSlurpClient::InboxControllerApi)
-    end
-  end
-
-  # unit tests for create_inbox
-  # Create an Inbox (email address)
-  # Create a new inbox and with a ranmdomized email address to send and receive from. Pass emailAddress parameter if you wish to use a specific email address. Creating an inbox is required before sending or receiving emails. If writing tests it is recommended that you create a new inbox during each test method so that it is unique and empty. 
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :description Optional description for an inbox.
-  # @option opts [String] :email_address Optional email address including domain you wish inbox to use (eg: test123@mydomain.com). Only supports domains that you have registered and verified with MailSlurp using dashboard or `createDomain` method.
-  # @option opts [DateTime] :expires_at Optional expires at timestamp. If your plan supports this feature you can specify when an inbox should expire. If left empty inbox will exist permanently or expire when your plan dictates
-  # @option opts [Boolean] :favourite Is inbox favourited.
-  # @option opts [String] :name Optional name for an inbox.
-  # @option opts [Array<String>] :tags Optional tags for an inbox. Can be used for searching and filtering inboxes.
-  # @return [Inbox]
-  describe 'create_inbox test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for delete_all_inboxes
-  # Delete all inboxes
-  # Permanently delete all inboxes and associated email addresses and all emails within the given inboxes
-  # @param [Hash] opts the optional parameters
-  # @return [nil]
-  describe 'delete_all_inboxes test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for delete_inbox
-  # Delete Inbox / Email Address
-  # Permanently delete an inbox and associated email address and all emails within the given inboxes
-  # @param inbox_id inboxId
-  # @param [Hash] opts the optional parameters
-  # @return [nil]
-  describe 'delete_inbox test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_all_inboxes
-  # List Inboxes Paginated
-  # List inboxes in paginated form. Allows for page index, page size, and sort direction. Can also filter by favourited or email address like pattern.
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :favourite Optionally filter results for favourites only
-  # @option opts [Integer] :page Optional page index in inbox list pagination
-  # @option opts [String] :search Optionally filter by search words partial matching ID, tags, name, and email address
-  # @option opts [Integer] :size Optional page size in inbox list pagination
-  # @option opts [String] :sort Optional createdAt sort direction ASC or DESC
-  # @return [PageInboxProjection]
-  describe 'get_all_inboxes test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_emails
-  # Get emails in an Inbox
-  # List emails that an inbox has received. Only emails that are sent to the inbox&#39;s email address will appear in the inbox. It may take several seconds for any email you send to an inbox&#39;s email address to appear in the inbox. To make this endpoint wait for a minimum number of emails use the &#x60;minCount&#x60; parameter. The server will retry the inbox database until the &#x60;minCount&#x60; is satisfied or the &#x60;retryTimeout&#x60; is reached
-  # @param inbox_id Id of inbox that emails belongs to
-  # @param [Hash] opts the optional parameters
-  # @option opts [Integer] :limit Limit the result set, ordered by received date time sort direction
-  # @option opts [Integer] :min_count Minimum acceptable email count. Will cause request to hang (and retry) until minCount is satisfied or retryTimeout is reached.
-  # @option opts [Integer] :retry_timeout Maximum milliseconds to spend retrying inbox database until minCount emails are returned
-  # @option opts [DateTime] :since Exclude emails received before this ISO 8601 date time
-  # @option opts [String] :sort Sort the results by received date and direction ASC or DESC
-  # @return [Array<EmailPreview>]
-  describe 'get_emails test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_inbox
-  # Get Inbox / EmailAddress
-  # Returns an inbox&#39;s properties, including its email address and ID.
-  # @param inbox_id inboxId
-  # @param [Hash] opts the optional parameters
-  # @return [Inbox]
-  describe 'get_inbox test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_inbox_emails_paginated
-  # Get inbox emails paginated
-  # Get a paginated list of emails in an inbox. Does not hold connections open.
-  # @param inbox_id Id of inbox that emails belongs to
-  # @param [Hash] opts the optional parameters
-  # @option opts [Integer] :page Optional page index in inbox emails list pagination
-  # @option opts [Integer] :size Optional page size in inbox emails list pagination
-  # @option opts [String] :sort Optional createdAt sort direction ASC or DESC
-  # @return [PageEmailPreview]
-  describe 'get_inbox_emails_paginated test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_inboxes
-  # List Inboxes / Email Addresses
-  # List the inboxes you have created
-  # @param [Hash] opts the optional parameters
-  # @return [Array<Inbox>]
-  describe 'get_inboxes test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for send_email
-  # Send Email
-  # Send an email from the inbox&#39;s email address. Specify the email recipients and contents in the request body. See the &#x60;SendEmailOptions&#x60; for more information. Note the &#x60;inboxId&#x60; refers to the inbox&#39;s id NOT its email address
-  # @param inbox_id ID of the inbox you want to send the email from
-  # @param [Hash] opts the optional parameters
-  # @option opts [SendEmailOptions] :send_email_options Options for the email
-  # @return [nil]
-  describe 'send_email test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for set_inbox_favourited
-  # Set inbox favourited state
-  # Set and return new favourite state for an inbox
-  # @param inbox_id inboxId
-  # @param set_inbox_favourited_options setInboxFavouritedOptions
-  # @param [Hash] opts the optional parameters
-  # @return [Inbox]
-  describe 'set_inbox_favourited test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end