vericred_client 0.0.9 → 0.0.11

data/docs/Pricing.md

@@ -1,18 +0,0 @@
-# VericredClient::Pricing
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**age** | **Integer** | Age of applicant | [optional] 
-**effective_date** | **Date** | Effective date of plan | [optional] 
-**expiration_date** | **Date** | Plan expiration date | [optional] 
-**plan_id** | **Integer** | Foreign key to plans | [optional] 
-**premium_child_only** | **Float** | Child-only premium | [optional] 
-**premium_family** | **Float** | Family premium | [optional] 
-**premium_single** | **Float** | Single-person premium | [optional] 
-**premium_single_and_children** | **Float** | Single person including children premium | [optional] 
-**premium_single_and_spouse** | **Float** | Person with spouse premium | [optional] 
-**premium_single_smoker** | **Float** | Premium for single smoker | [optional] 
-**rating_area_id** | **String** | Foreign key to rating areas | [optional] 
-
-

data/spec/models/pricing_spec.rb

@@ -1,220 +0,0 @@
-=begin
-#Vericred API
-
-#Vericred's API allows you to search for Health Plans that a specific doctor
-accepts.
-
-## Getting Started
-
-Visit our [Developer Portal](https://vericred.3scale.net) to
-create an account.
-
-Once you have created an account, you can create one Application for
-Production and another for our Sandbox (select the appropriate Plan when
-you create the Application).
-
-## Authentication
-
-To authenticate, pass the API Key you created in the Developer Portal as
-a `Vericred-Api-Key` header.
-
-`curl -H 'Vericred-Api-Key: YOUR_KEY' "https://api.vericred.com/providers?search_term=Foo&zip_code=11215"`
-
-## Versioning
-
-Vericred's API default to the latest version.  However, if you need a specific
-version, you can request it with an `Accept-Version` header.
-
-The current version is `v3`.  Previous versions are `v1` and `v2`.
-
-`curl -H 'Vericred-Api-Key: YOUR_KEY' -H 'Accept-Version: v2' "https://api.vericred.com/providers?search_term=Foo&zip_code=11215"`
-
-## Pagination
-
-Endpoints that accept `page` and `per_page` parameters are paginated. They expose
-four additional fields that contain data about your position in the response,
-namely `Total`, `Per-Page`, `Link`, and `Page` as described in [RFC-5988](https://tools.ietf.org/html/rfc5988).
-
-For example, to display 5 results per page and view the second page of a
-`GET` to `/networks`, your final request would be `GET /networks?....page=2&per_page=5`.
-
-## Sideloading
-
-When we return multiple levels of an object graph (e.g. `Provider`s and their `State`s
-we sideload the associated data.  In this example, we would provide an Array of
-`State`s and a `state_id` for each provider.  This is done primarily to reduce the
-payload size since many of the `Provider`s will share a `State`
-
-```
-{
-  providers: [{ id: 1, state_id: 1}, { id: 2, state_id: 1 }],
-  states: [{ id: 1, code: 'NY' }]
-}
-```
-
-If you need the second level of the object graph, you can just match the
-corresponding id.
-
-## Selecting specific data
-
-All endpoints allow you to specify which fields you would like to return.
-This allows you to limit the response to contain only the data you need.
-
-For example, let's take a request that returns the following JSON by default
-
-```
-{
-  provider: {
-    id: 1,
-    name: 'John',
-    phone: '1234567890',
-    field_we_dont_care_about: 'value_we_dont_care_about'
-  },
-  states: [{
-    id: 1,
-    name: 'New York',
-    code: 'NY',
-    field_we_dont_care_about: 'value_we_dont_care_about'
-  }]
-}
-```
-
-To limit our results to only return the fields we care about, we specify the
-`select` query string parameter for the corresponding fields in the JSON
-document.
-
-In this case, we want to select `name` and `phone` from the `provider` key,
-so we would add the parameters `select=provider.name,provider.phone`.
-We also want the `name` and `code` from the `states` key, so we would
-add the parameters `select=states.name,staes.code`.  The id field of
-each document is always returned whether or not it is requested.
-
-Our final request would be `GET /providers/12345?select=provider.name,provider.phone,states.name,states.code`
-
-The response would be
-
-```
-{
-  provider: {
-    id: 1,
-    name: 'John',
-    phone: '1234567890'
-  },
-  states: [{
-    id: 1,
-    name: 'New York',
-    code: 'NY'
-  }]
-}
-```
-
-
-
-OpenAPI spec version: 1.0.0
-
-Generated by: https://github.com/swagger-api/swagger-codegen.git
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
-
-=end
-
-require 'spec_helper'
-require 'json'
-require 'date'
-
-# Unit tests for VericredClient::Pricing
-# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
-# Please update as you see appropriate
-describe 'Pricing' do
-  before do
-    # run before each test
-    @instance = VericredClient::Pricing.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of Pricing' do
-    it 'should create an instact of Pricing' do
-      expect(@instance).to be_instance_of(VericredClient::Pricing)
-    end
-  end
-  describe 'test attribute "age"' do
-    it 'should work' do
-       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  describe 'test attribute "effective_date"' do
-    it 'should work' do
-       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  describe 'test attribute "expiration_date"' do
-    it 'should work' do
-       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  describe 'test attribute "plan_id"' do
-    it 'should work' do
-       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  describe 'test attribute "premium_child_only"' do
-    it 'should work' do
-       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  describe 'test attribute "premium_family"' do
-    it 'should work' do
-       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  describe 'test attribute "premium_single"' do
-    it 'should work' do
-       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  describe 'test attribute "premium_single_and_children"' do
-    it 'should work' do
-       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  describe 'test attribute "premium_single_and_spouse"' do
-    it 'should work' do
-       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  describe 'test attribute "premium_single_smoker"' do
-    it 'should work' do
-       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  describe 'test attribute "rating_area_id"' do
-    it 'should work' do
-       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end
-