pepipost_gem 2.5.0 → 5.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 3b7d3643dbb6d993e1cb1a312c1ea16c036782e7
-  data.tar.gz: d4212c3932c2a138dc45bfd76985ac579c1e3fe0
+  metadata.gz: ffbd1f3d8c521640487d030257c4ca12e2706dcb
+  data.tar.gz: f5128832bc126caf75fc4b1a16c096385ada50f0
 SHA512:
-  metadata.gz: 2c255f736b76d2e5337efc58c8e322801c4ebd3648e146c48b13c508d16c572fe3c608669cc8f072abc6a04eb35402f1e09455aea7a23a1c18065d0839e3d63e
-  data.tar.gz: c7c9a87fe5b4f7da863c41a69859d1304ea0e6b9f004f1b475e9b91b6bcac6854504a08c1d20a2a3861092365fa92028523f965bedd16a33e2532ab93b7f016c
+  metadata.gz: 6c716c649ee1991e028ad64b1fcd1fdda292e5cc86e416c663fac577a3859d3b249beb767c0b44631de0e8a7f92808af6e8c6cf526e393c05b00dc12009181c7
+  data.tar.gz: 03680023eca0b81f64e95cc7330a295c925da65019c654949e4c3d2b9d2a9a7055f2bb52acb3714737a14ae4c9558fe275fc23f46fb6c7aed3c6a1883a6a379d

data/LICENSE

@@ -1,9 +1,6 @@
-License: 
-========
-The MIT License (MIT)
-http://opensource.org/licenses/MIT
+MIT License
 
-Copyright (c) 2014 - 2016 APIMATIC Limited
+Copyright (c) 2018 Pepipost
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -12,17 +9,13 @@ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
 copies of the Software, and to permit persons to whom the Software is
 furnished to do so, subject to the following conditions:
 
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
-
-Trade Mark:
-==========
-APIMATIC is a trade mark for APIMATIC Limited
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

data/README.md

@@ -1,141 +1,187 @@
-# Getting started
-
-Pepipost is a cloud-based SMTP relay service that delivers highly personalised transactional emails to the inbox within seconds of your customer’s transaction
+![pepipostlogo](https://pepipost.com/wp-content/uploads/2017/07/P_LOGO.png)
 
-## How to Build
+[![Gem Version](https://badge.fury.io/rb/pepipost_gem.svg)](https://badge.fury.io/rb/pepipost_gem)
+[![Open Source Helpers](https://www.codetriage.com/pepipost/pepipost-sdk-ruby/badges/users.svg)](https://www.codetriage.com/pepipost/pepipost-sdk-ruby)
+[![MIT licensed](https://img.shields.io/badge/license-MIT-blue.svg)](./LICENSE.txt)
+[![Twitter Follow](https://img.shields.io/twitter/follow/pepi_post.svg?style=social&label=Follow)](https://twitter.com/pepi_post)
 
-This client library is a Ruby gem which can be compiled and used in your Ruby and Ruby on Rails project. This library requires a few gems from the RubyGems repository.
+# Ruby SDK :gem: for [Pepipost](http://www.pepipost.com/?utm_campaign=GitHubSDK&utm_medium=GithubSDK&utm_source=GithubSDK)
 
-1. Open the command line interface or the terminal and navigate to the folder containing the source code.
-2. Run ``` gem build pepipost_gem.gemspec ``` to build the gem.
-3. Once built, the gem can be installed on the current work environment using ``` gem install pepipost_gem-2.5.0.gem ```
+This gem contains methods for easily interacting with the Pepipost Email Sending API to send emails within few seconds.
 
-![Building Gem](https://apidocs.io/illustration/ruby?step=buildSDK&workspaceFolder=pepipost_gem-Ruby&workspaceName=pepipost_gem-Ruby&projectName=pepipost_gem&gemName=pepipost_gem&gemVer=2.5.0)
+We are trying to make our libraries a Community Driven. To help us building right things in proper order we would request you to help us by sharing comments, creating new issues or pull request.
 
-## How to Use
+## Table of Content
+* [Installation](#installation)
+* [Quick Start](#quickstart)
+* [Sample Example](#steps)
+* [Announcements](#announcements)
+* [Roadmap](#roadmap)
+* [About](#about)
+* [License](#license)
 
-The following section explains how to use the PepipostGem Ruby Gem in a new Rails project using RubyMine™. The basic workflow presented here is also applicable if you prefer using a different editor or IDE.
 
-### 1. Starting a new project
+<a name="installation"></a>
+## Installation 
 
-Close any existing projects in RubyMine&trade; by selecting ``` File -> Close Project ```. Next, click on ``` Create New Project ``` to create a new project from scratch.
+### Manually generate your own pepipost gem 
 
-![Create a new project in RubyMine](https://apidocs.io/illustration/ruby?step=createNewProject0&workspaceFolder=pepipost_gem-Ruby&workspaceName=PepipostGem&projectName=pepipost_gem&gemName=pepipost_gem&gemVer=2.5.0)
+This client library is a Ruby gem which can be compiled and used in your Ruby on Rails project. This library requires a few gems from the RubyGems repository.
 
-Next, provide ``` TestApp ``` as the project name, choose ``` Rails Application ``` as the project type, and click ``` OK ```.
+* Open the command line interface/terminal and navigate to the folder of your choice and run the below commands to download and navigate to the downloaded folder:
+``` git clone https://github.com/pepipost/pepipost-sdk-ruby.git ```
+* ``` cd pepipost-sdk-ruby ``` 
 
-![Create a new Rails Application in RubyMine - step 1](https://apidocs.io/illustration/ruby?step=createNewProject1&workspaceFolder=pepipost_gem-Ruby&workspaceName=PepipostGem&projectName=pepipost_gem&gemName=pepipost_gem&gemVer=2.5.0)
+* ``` gem build pepipost.gemspec ``` to build the gem.
+* ``` gem install pepipost-5.0.0.gem ``` to install pepipost gem
 
-In the next dialog make sure that correct *Ruby SDK* is being used (minimum 2.0.0) and click ``` OK ```.
+![Building Gem](https://apidocs.io/illustration/ruby?step=buildSDK&workspaceFolder=pepipost-Ruby&workspaceName=pepipost-Ruby&projectName=pepipost_gem&gemName=pepipost&gemVer=5.0.0)
 
-![Create a new Rails Application in RubyMine - step 2](https://apidocs.io/illustration/ruby?step=createNewProject2&workspaceFolder=pepipost_gem-Ruby&workspaceName=PepipostGem&projectName=pepipost_gem&gemName=pepipost_gem&gemVer=2.5.0)
+Once pepipost_gem is installed, use the sample example to [send test email](#steps). 
 
-This will create a new Rails Application project with an existing set of files and folder.
+<a name="quickstart"></a>
+## Quickstart
 
-### 2. Add reference of the gem
+The following section explains how to use the Pepipost Gem in a new Rails project using RubyMine.
 
-In order to use the PepipostGem gem in the new project we must add a gem reference. Locate the ```Gemfile``` in the *Project Explorer* window under the ``` TestApp ``` project node. The file contains references to all gems being used in the project. Here, add the reference to the library gem by adding the following line: ``` gem 'pepipost_gem', '~> 2.5.0' ```
+The basic workflow presented here is also applicable if you prefer using a different editor or IDE.
 
-![Add references of the Gemfile](https://apidocs.io/illustration/ruby?step=addReference&workspaceFolder=pepipost_gem-Ruby&workspaceName=PepipostGem&projectName=pepipost_gem&gemName=pepipost_gem&gemVer=2.5.0)
+1. Starting a new project
 
-### 3. Adding a new Rails Controller
+   Close any existing projects in RubyMine by selecting:
 
-Once the ``` TestApp ``` project is created, a folder named ``` controllers ``` will be visible in the *Project Explorer* under the following path: ``` TestApp > app > controllers ```. Right click on this folder and select ``` New -> Run Rails Generator... ```.
+   * ``` File -> Close Project ``` 
+   * Next, click on ``` Create New Project ``` to create a new project from scratch.
 
-![Run Rails Generator on Controllers Folder](https://apidocs.io/illustration/ruby?step=addCode0&workspaceFolder=pepipost_gem-Ruby&workspaceName=PepipostGem&projectName=pepipost_gem&gemName=pepipost_gem&gemVer=2.5.0)
+   ![Create a new project in RubyMine](https://apidocs.io/illustration/ruby?step=createNewProject0&workspaceFolder=pepipost_gem-Ruby&workspaceName=PepipostGem&projectName=pepipost_gem&gemName=pepipost_gem&gemVer=2.5.0)
 
-Selecting the said option will popup a small window where the generator names are displayed. Here, select the ``` controller ``` template.
+   * Next, provide ``` TestApp ``` as the project name.
+   * Choose ``` Rails Application ``` as the project type.
+   * Click ``` OK ```.
 
-![Create a new Controller](https://apidocs.io/illustration/ruby?step=addCode1&workspaceFolder=pepipost_gem-Ruby&workspaceName=PepipostGem&projectName=pepipost_gem&gemName=pepipost_gem&gemVer=2.5.0)
+   ![Create a new Rails Application in RubyMine - step 1](https://apidocs.io/illustration/ruby?step=createNewProject1&workspaceFolder=pepipost_gem-Ruby&workspaceName=PepipostGem&projectName=pepipost_gem&gemName=pepipost_gem&gemVer=2.5.0)
 
-Next, a popup window will ask you for a Controller name and included Actions. For controller name provide ``` Hello ``` and include an action named ``` Index ``` and click ``` OK ```.
+     In the next dialog make sure that correct *Ruby SDK* is being used (minimum 2.0.0) 
+   * click ``` OK ```.
 
-![Add a new Controller](https://apidocs.io/illustration/ruby?step=addCode2&workspaceFolder=pepipost_gem-Ruby&workspaceName=PepipostGem&projectName=pepipost_gem&gemName=pepipost_gem&gemVer=2.5.0)
+   ![Create a new Rails Application in RubyMine - step 2](https://apidocs.io/illustration/ruby?step=createNewProject2&workspaceFolder=pepipost_gem-Ruby&workspaceName=PepipostGem&projectName=pepipost_gem&gemName=pepipost_gem&gemVer=2.5.0)
 
-A new controller class anmed ``` HelloController ``` will be created in a file named ``` hello_controller.rb ``` containing a method named ``` Index ```. In this method, add code for initialization and a sample for its usage.
+   This will create a new Rails Application project with an existing set of files and folder.
 
-![Initialize the library](https://apidocs.io/illustration/ruby?step=addCode3&workspaceFolder=pepipost_gem-Ruby&workspaceName=PepipostGem&projectName=pepipost_gem&gemName=pepipost_gem&gemVer=2.5.0)
+2. Add reference of the gem
+   
+   * In order to use the Pepipost gem in the new project, add a gem reference.
+   * Locate the ```Gemfile``` in the *Project Explorer* window under the ``` TestApp ``` project node.
+   * The file contains references to all gems being used in the project. Here, add the reference to the library gem by adding the following line:
+    ``` gem 'pepipost_gem', '~> 2.5.0' ```
 
-## How to Test
+   ![Add references of the Gemfile](https://apidocs.io/illustration/ruby?step=addReference&workspaceFolder=pepipost_gem-Ruby&workspaceName=PepipostGem&projectName=pepipost_gem&gemName=pepipost_gem&gemVer=2.5.0)
 
-You can test the generated SDK and the server with automatically generated test
-cases as follows:
+3. Adding a new Rails Controller
 
-  1. From terminal/cmd navigate to the root directory of the SDK.
-  2. Invoke: `bundle exec rake`
+   * Once the ``` TestApp ``` project is created.
+   * Folder named ``` controllers ``` will be visible in the *Project Explorer* under the following path:
+     ``` TestApp > app > controllers ```. 
+   * Right click on this folder.
+   * select ``` New -> Run Rails Generator ```.
 
-## Initialization
+   ![Run Rails Generator on Controllers Folder](https://apidocs.io/illustration/ruby?step=addCode0&workspaceFolder=pepipost_gem-Ruby&workspaceName=PepipostGem&projectName=pepipost_gem&gemName=pepipost_gem&gemVer=2.5.0)
 
-### 
+   * Selecting the said option will popup a small window where the generator names are displayed.
+   * select the ``` controller ``` template.
 
-API client can be initialized as following.
+   ![Create a new Controller](https://apidocs.io/illustration/ruby?step=addCode1&workspaceFolder=pepipost_gem-Ruby&workspaceName=PepipostGem&projectName=pepipost_gem&gemName=pepipost_gem&gemVer=2.5.0)
 
-```ruby
-
-client = PepipostGem::PepipostGemClient.new
-```
+   * A  popup window will ask you for a Controller name and included Actions.
+   * For controller name provide ``` Hello ```.
+   * Include an action named ``` Index ```. 
+   * Click ``` OK ```.
 
-The added initlization code can be debugged by putting a breakpoint in the ``` Index ``` method and running the project in debug mode by selecting ``` Run -> Debug 'Development: TestApp' ```.
+   ![Add a new Controller](https://apidocs.io/illustration/ruby?step=addCode2&workspaceFolder=pepipost_gem-Ruby&workspaceName=PepipostGem&projectName=pepipost_gem&gemName=pepipost_gem&gemVer=2.5.0)
 
-![Debug the TestApp](https://apidocs.io/illustration/ruby?step=addCode4&workspaceFolder=pepipost_gem-Ruby&workspaceName=PepipostGem&projectName=pepipost_gem&gemName=pepipost_gem&gemVer=2.5.0&initLine=client%2520%253D%2520PepipostGemClient.new)
+   * A new controller class anmed ``` HelloController ``` will be created in a file named ``` hello_controller.rb ``` containing a method named ``` Index ```.
+   * In this method, copy [sample example](#steps).
+   * Run your project.
 
+   ![Initialize the library](https://apidocs.io/illustration/ruby?step=addCode3&workspaceFolder=pepipost_gem-Ruby&workspaceName=PepipostGem&projectName=pepipost_gem&gemName=pepipost_gem&gemVer=2.5.0)
 
+<a name="steps"></a>
+## Usage
 
-# Class Reference
-
-## <a name="list_of_controllers"></a>List of Controllers
+```ruby
+require 'pepipost'
+require 'json'
 
-* [EmailController](#email_controller)
+include Pepipost
 
-## <a name="email_controller"></a>![Class: ](https://apidocs.io/img/class.png ".EmailController") EmailController
+api_key = 'Your api_key here'
 
-### Get singleton instance
+client = PepipostClient.new(api_key: api_key)
 
-The singleton instance of the ``` EmailController ``` class can be accessed from the API Client.
+mail_send_controller = client.mail_send
 
-```ruby
-email_controller = client.email
-```
+body = Send.new
 
-### <a name="create_send_email"></a>![Method: ](https://apidocs.io/img/method.png ".EmailController.create_send_email") create_send_email
+body.from = From.new
 
-> *Tags:*  ``` Skips Authentication ``` 
+body.from.email = 'hello@your-register-domain-with-pepipost'
+body.from.name = 'Example Pepi'
+body.subject = 'Emailing with Pepipost is easy'
+body.content = []
 
-> This Endpoint sends emails with the credentials passed.
+body.content[0] = Content.new
 
+body.content[0].type = TypeEnum::HTML
+body.content[0].value = '<html><body>Hey,<br><br>Do you know integration is even simpler in Pepipost, <br>with Ruby <br> Happy Mailing ! <br><br>Pepipost </body></html>'
 
-```ruby
-def create_send_email(api_key = nil,
-                          body = nil); end
-```
 
-#### Parameters
+body.personalizations = []
 
-| Parameter | Tags | Description |
-|-----------|------|-------------|
-| api_key |  ``` Optional ```  | Generated header parameter. Example value ='5ce7096ed4bf2b39dfa932ff5fa84ed9ed8' |
-| body |  ``` Optional ```  | The body passed will be json format. |
+body.personalizations[0] = Personalizations.new
 
+body.personalizations[0].to = []
 
-#### Example Usage
+body.personalizations[0].to[0] = EmailStruct.new
 
-```ruby
-api_key = 'api_key'
-body = EmailBody.new
+body.personalizations[0].to[0].name = 'random-1'
+body.personalizations[0].to[0].email = 'random-1@mydomain.name'
 
-result = email_controller.create_send_email(api_key, body)
+begin
+  result = mail_send_controller.create_generatethemailsendrequest(body)
+  puts (result)
+rescue APIException => ex
+  puts "Caught APIException: #{ex.message}"
+end
 
 ```
 
-#### Errors
+* Change your api-key and sending domain respectively
+  * **apikey** will be available under Login to Pepipost -> Settings -> Integration  
+  * **Sending Domain** will be available under Login to Pepiost -> Settings -> Sending Domains 
+  
+```
+  *Note :: Domains showing with Active status on Sending Domain dashboard are only allowed to send any sort of emails.* In case there are no Sending Domain added under your account, then first add the domain, get the DNS (SPF/DKIM) settings done and get it reviewed by our compliance team for approval. Once the domain is approved, it will be in ACTIVE status and will be ready to send any sort of emails. 
+```
+* Save above file as sendEmail.rb
+* run ``` ruby sendEmail.rb ```
 
-| Error Code | Error Description |
-|------------|-------------------|
-| 405 | Method not allowed |
+<a name="announcements"></a>
+# Announcements
 
+v5.0 has been released! Please see the [release notes](https://github.com/pepipost/pepipost-sdk-ruby/releases/) for details.
 
+All updates to this library are documented in our [releases](https://github.com/pepipost/pepipost-sdk-ruby/releases). For any queries, feel free to reach out us at dx@pepipost.com
 
-[Back to List of Controllers](#list_of_controllers)
+<a name="roadmap"></a>
+## Roadmap
 
+If you are interested in the future direction of this project, please take a look at our open [issues](https://github.com/pepipost/pepipost-sdk-ruby/issues) and [pull requests](https://github.com/pepipost/pepipost-sdk-ruby/pulls). We would love to hear your feedback.
 
+<a name="about"></a>
+## About
+pepipost-sdk-ruby library is guided and supported by the [Pepipost Developer Experience Team](https://github.com/orgs/pepipost/teams/pepis/members) .
+This pepipost gem is maintained and funded by Pepipost Ltd. The names and logos for pepipost gem are trademarks of Pepipost Ltd.
 
+<a name="license"></a>
+## License
+This code library was semi-automatically generated by APIMATIC v2.0 and licensed under The MIT License (MIT).

data/lib/pepipost.rb

@@ -0,0 +1,74 @@
+# pepipost
+#
+# This file was automatically generated by APIMATIC v2.0 (
+# https://apimatic.io ).
+
+require 'date'
+require 'json'
+require 'faraday'
+require 'certifi'
+require 'logging'
+
+require_relative 'pepipost/api_helper.rb'
+require_relative 'pepipost/pepipost_client.rb'
+
+# Http
+require_relative 'pepipost/http/http_call_back.rb'
+require_relative 'pepipost/http/http_client.rb'
+require_relative 'pepipost/http/http_method_enum.rb'
+require_relative 'pepipost/http/http_request.rb'
+require_relative 'pepipost/http/http_response.rb'
+require_relative 'pepipost/http/http_context.rb'
+require_relative 'pepipost/http/faraday_client.rb'
+require_relative 'pepipost/http/auth/custom_header_auth.rb'
+
+# Models
+require_relative 'pepipost/models/base_model.rb'
+require_relative 'pepipost/models/content.rb'
+require_relative 'pepipost/models/personalizations.rb'
+require_relative 'pepipost/models/from.rb'
+require_relative 'pepipost/models/settings.rb'
+require_relative 'pepipost/models/email_struct.rb'
+require_relative 'pepipost/models/attachments.rb'
+require_relative 'pepipost/models/send.rb'
+require_relative 'pepipost/models/domain_struct.rb'
+require_relative 'pepipost/models/delete_domain.rb'
+require_relative 'pepipost/models/add_email_or_domain_to_suppression_list.rb'
+require_relative 'pepipost/models/remove_email_or_domain_to_suppression_list.rb'
+require_relative 'pepipost/models/create_subaccount.rb'
+require_relative 'pepipost/models/update_subaccount.rb'
+require_relative 'pepipost/models/update_credis_of_subaccount.rb'
+require_relative 'pepipost/models/update_recurring_credis_of_subaccount.rb'
+require_relative 'pepipost/models/delete_subacoount.rb'
+require_relative 'pepipost/models/enable_or_disable_subacoount.rb'
+require_relative 'pepipost/models/type_enum.rb'
+require_relative 'pepipost/models/action_enum.rb'
+require_relative 'pepipost/models/aggregated_by_enum.rb'
+require_relative 'pepipost/models/events_enum.rb'
+require_relative 'pepipost/models/sort_enum.rb'
+require_relative 'pepipost/models/timeperiod_enum.rb'
+
+# Exceptions
+require_relative 'pepipost/exceptions/api_exception.rb'
+
+require_relative 'pepipost/configuration.rb'
+
+# Controllers
+require_relative 'pepipost/controllers/base_controller.rb'
+require_relative 'pepipost/controllers/mail_send_controller.rb'
+require_relative 'pepipost/controllers/events_controller.rb'
+require_relative 'pepipost/controllers/stats_controller.rb'
+require_relative 'pepipost/controllers/subaccounts_controller.rb'
+require_relative 'pepipost/controllers/subaccounts_delete_controller.rb'
+require_relative 'pepipost/controllers/subaccounts_get_sub_accounts' \
+                 '_controller.rb'
+require_relative 'pepipost/controllers/setrecurringcreditddetails_controller.rb'
+require_relative 'pepipost/controllers/subaccounts_setsubaccountcredit' \
+                 '_controller.rb'
+require_relative 'pepipost/controllers/subaccounts_update_subaccount' \
+                 '_controller.rb'
+require_relative 'pepipost/controllers/subaccounts_create_subaccount' \
+                 '_controller.rb'
+require_relative 'pepipost/controllers/suppression_controller.rb'
+require_relative 'pepipost/controllers/domain_delete_controller.rb'
+require_relative 'pepipost/controllers/domain_controller.rb'

data/lib/{pepipost_gem → pepipost}/api_helper.rb

@@ -1,7 +1,9 @@
-# This file was automatically generated by APIMATIC v2.0
-# ( https://apimatic.io ).
+# pepipost
+#
+# This file was automatically generated by APIMATIC v2.0 (
+# https://apimatic.io ).
 
-module PepipostGem
+module Pepipost
   # API utility class
   class APIHelper
     # Serializes an array parameter (creates key value pairs).

data/lib/pepipost/configuration.rb

@@ -0,0 +1,24 @@
+# pepipost
+#
+# This file was automatically generated by APIMATIC v2.0 (
+# https://apimatic.io ).
+
+# CohesityManagementSdk
+module Pepipost
+  # All configuration including auth info and base URI for the API access
+  # are configured in this class.
+  class Configuration
+    # The base Uri for API calls
+    @base_uri = 'https://api.pepipost.com/v5'
+
+    # Your Pepipost API Key. You will find the api key in the Pepipost application in Integrations.
+    @api_key = 'TODO: Replace'
+
+    # The attribute accessors for public properties.
+    class << self
+      attr_accessor :array_serialization
+      attr_accessor :base_uri
+      attr_accessor :api_key
+    end
+  end
+end

data/lib/{pepipost_gem → pepipost}/controllers/base_controller.rb

@@ -1,7 +1,9 @@
-# This file was automatically generated by APIMATIC v2.0
-# ( https://apimatic.io ).
+# pepipost
+#
+# This file was automatically generated by APIMATIC v2.0 (
+# https://apimatic.io ).
 
-module PepipostGem
+module Pepipost
   # Base controller.
   class BaseController
     attr_accessor :http_client, :http_call_back
@@ -42,8 +44,11 @@ module PepipostGem
     end
 
     def validate_response(context)
- #     raise APIException.new 'HTTP Response Not OK', context unless
-  #      context.response.status_code.between?(200, 208) # [200,208] = HTTP OK
+      if context.response.status_code == 400 || context.response.status_code == 401 || context.response.status_code == 403
+        return 1
+      end
+      raise APIException.new 'HTTP Response Not OK', context unless
+        context.response.status_code.between?(200, 208) # [200,208] = HTTP OK
     end
   end
 end