vericred_client 0.0.6 → 0.0.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (65) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +26 -20
  3. data/docs/CarrierSubsidiary.md +1 -0
  4. data/docs/DrugsApi.md +20 -14
  5. data/docs/NetworksApi.md +17 -4
  6. data/docs/Plan.md +3 -0
  7. data/docs/PlanCounty.md +0 -1
  8. data/docs/PlanCountyBulk.md +0 -1
  9. data/docs/PlanSearchResult.md +3 -0
  10. data/docs/PlanZipCounty.md +10 -0
  11. data/docs/PlansApi.md +17 -2
  12. data/docs/ProvidersApi.md +18 -8
  13. data/docs/RequestPlanFind.md +3 -0
  14. data/docs/ZipCountiesApi.md +10 -7
  15. data/lib/vericred_client/api/drugs_api.rb +7 -18
  16. data/lib/vericred_client/api/networks_api.rb +14 -13
  17. data/lib/vericred_client/api/plans_api.rb +24 -13
  18. data/lib/vericred_client/api/providers_api.rb +7 -15
  19. data/lib/vericred_client/api/zip_counties_api.rb +6 -14
  20. data/lib/vericred_client/api_client.rb +6 -10
  21. data/lib/vericred_client/api_error.rb +5 -10
  22. data/lib/vericred_client/configuration.rb +7 -0
  23. data/lib/vericred_client/models/applicant.rb +5 -10
  24. data/lib/vericred_client/models/base.rb +5 -10
  25. data/lib/vericred_client/models/carrier.rb +5 -10
  26. data/lib/vericred_client/models/carrier_subsidiary.rb +19 -14
  27. data/lib/vericred_client/models/county.rb +5 -10
  28. data/lib/vericred_client/models/county_bulk.rb +5 -10
  29. data/lib/vericred_client/models/drug.rb +5 -10
  30. data/lib/vericred_client/models/drug_coverage.rb +5 -10
  31. data/lib/vericred_client/models/drug_coverage_response.rb +5 -10
  32. data/lib/vericred_client/models/drug_package.rb +5 -10
  33. data/lib/vericred_client/models/drug_search_response.rb +5 -10
  34. data/lib/vericred_client/models/meta.rb +5 -10
  35. data/lib/vericred_client/models/network.rb +5 -10
  36. data/lib/vericred_client/models/network_search_response.rb +5 -10
  37. data/lib/vericred_client/models/plan.rb +36 -11
  38. data/lib/vericred_client/models/plan_county.rb +6 -21
  39. data/lib/vericred_client/models/plan_county_bulk.rb +6 -21
  40. data/lib/vericred_client/models/plan_search_response.rb +5 -10
  41. data/lib/vericred_client/models/plan_search_result.rb +36 -11
  42. data/lib/vericred_client/models/plan_zip_county.rb +313 -0
  43. data/lib/vericred_client/models/pricing.rb +5 -10
  44. data/lib/vericred_client/models/provider.rb +5 -10
  45. data/lib/vericred_client/models/provider_show_response.rb +5 -10
  46. data/lib/vericred_client/models/providers_search_response.rb +5 -10
  47. data/lib/vericred_client/models/rating_area.rb +5 -10
  48. data/lib/vericred_client/models/request_plan_find.rb +36 -11
  49. data/lib/vericred_client/models/request_plan_find_applicant.rb +5 -10
  50. data/lib/vericred_client/models/request_plan_find_provider.rb +5 -10
  51. data/lib/vericred_client/models/request_providers_search.rb +5 -10
  52. data/lib/vericred_client/models/state.rb +5 -10
  53. data/lib/vericred_client/models/zip_code.rb +5 -10
  54. data/lib/vericred_client/models/zip_counties_response.rb +5 -10
  55. data/lib/vericred_client/models/zip_county.rb +5 -10
  56. data/lib/vericred_client/models/zip_county_bulk.rb +5 -10
  57. data/lib/vericred_client/models/zip_county_response.rb +5 -10
  58. data/lib/vericred_client/version.rb +6 -11
  59. data/lib/vericred_client.rb +6 -10
  60. data/spec/api/drugs_api_spec.rb +5 -12
  61. data/spec/api/networks_api_spec.rb +8 -11
  62. data/spec/api/plans_api_spec.rb +14 -11
  63. data/spec/api/providers_api_spec.rb +5 -11
  64. data/spec/api/zip_counties_api_spec.rb +5 -11
  65. metadata +4 -2
@@ -31,17 +31,12 @@ The current version is `v3`. Previous versions are `v1` and `v2`.
31
31
 
32
32
  ## Pagination
33
33
 
34
- Most endpoints are not paginated. It will be noted in the documentation if/when
35
- an endpoint is paginated.
34
+ Endpoints that accept `page` and `per_page` parameters are paginated. They expose
35
+ four additional fields that contain data about your position in the response,
36
+ namely `Total`, `Per-Page`, `Link`, and `Page` as described in [RFC-5988](https://tools.ietf.org/html/rfc5988).
36
37
 
37
- When pagination is present, a `meta` stanza will be present in the response
38
- with the total number of records
39
-
40
- ```
41
- {
42
- things: [{ id: 1 }, { id: 2 }],
43
- meta: { total: 500 }
44
- }
38
+ For example, to display 5 results per page and view the second page of a
39
+ `GET` to `/networks`, your final request would be `GET /networks?....page=2&per_page=5`.
45
40
  ```
46
41
 
47
42
  ## Sideloading
@@ -31,17 +31,12 @@ The current version is `v3`. Previous versions are `v1` and `v2`.
31
31
 
32
32
  ## Pagination
33
33
 
34
- Most endpoints are not paginated. It will be noted in the documentation if/when
35
- an endpoint is paginated.
34
+ Endpoints that accept `page` and `per_page` parameters are paginated. They expose
35
+ four additional fields that contain data about your position in the response,
36
+ namely `Total`, `Per-Page`, `Link`, and `Page` as described in [RFC-5988](https://tools.ietf.org/html/rfc5988).
36
37
 
37
- When pagination is present, a `meta` stanza will be present in the response
38
- with the total number of records
39
-
40
- ```
41
- {
42
- things: [{ id: 1 }, { id: 2 }],
43
- meta: { total: 500 }
44
- }
38
+ For example, to display 5 results per page and view the second page of a
39
+ `GET` to `/networks`, your final request would be `GET /networks?....page=2&per_page=5`.
45
40
  ```
46
41
 
47
42
  ## Sideloading
@@ -31,17 +31,12 @@ The current version is `v3`. Previous versions are `v1` and `v2`.
31
31
 
32
32
  ## Pagination
33
33
 
34
- Most endpoints are not paginated. It will be noted in the documentation if/when
35
- an endpoint is paginated.
34
+ Endpoints that accept `page` and `per_page` parameters are paginated. They expose
35
+ four additional fields that contain data about your position in the response,
36
+ namely `Total`, `Per-Page`, `Link`, and `Page` as described in [RFC-5988](https://tools.ietf.org/html/rfc5988).
36
37
 
37
- When pagination is present, a `meta` stanza will be present in the response
38
- with the total number of records
39
-
40
- ```
41
- {
42
- things: [{ id: 1 }, { id: 2 }],
43
- meta: { total: 500 }
44
- }
38
+ For example, to display 5 results per page and view the second page of a
39
+ `GET` to `/networks`, your final request would be `GET /networks?....page=2&per_page=5`.
45
40
  ```
46
41
 
47
42
  ## Sideloading
@@ -31,17 +31,12 @@ The current version is `v3`. Previous versions are `v1` and `v2`.
31
31
 
32
32
  ## Pagination
33
33
 
34
- Most endpoints are not paginated. It will be noted in the documentation if/when
35
- an endpoint is paginated.
34
+ Endpoints that accept `page` and `per_page` parameters are paginated. They expose
35
+ four additional fields that contain data about your position in the response,
36
+ namely `Total`, `Per-Page`, `Link`, and `Page` as described in [RFC-5988](https://tools.ietf.org/html/rfc5988).
36
37
 
37
- When pagination is present, a `meta` stanza will be present in the response
38
- with the total number of records
39
-
40
- ```
41
- {
42
- things: [{ id: 1 }, { id: 2 }],
43
- meta: { total: 500 }
44
- }
38
+ For example, to display 5 results per page and view the second page of a
39
+ `GET` to `/networks`, your final request would be `GET /networks?....page=2&per_page=5`.
45
40
  ```
46
41
 
47
42
  ## Sideloading
@@ -124,5 +119,5 @@ Generated by: https://github.com/swagger-api/swagger-codegen.git
124
119
  =end
125
120
 
126
121
  module VericredClient
127
- VERSION = "0.0.6"
122
+ VERSION = "0.0.7"
128
123
  end
@@ -31,17 +31,12 @@ The current version is `v3`. Previous versions are `v1` and `v2`.
31
31
 
32
32
  ## Pagination
33
33
 
34
- Most endpoints are not paginated. It will be noted in the documentation if/when
35
- an endpoint is paginated.
34
+ Endpoints that accept `page` and `per_page` parameters are paginated. They expose
35
+ four additional fields that contain data about your position in the response,
36
+ namely `Total`, `Per-Page`, `Link`, and `Page` as described in [RFC-5988](https://tools.ietf.org/html/rfc5988).
36
37
 
37
- When pagination is present, a `meta` stanza will be present in the response
38
- with the total number of records
39
-
40
- ```
41
- {
42
- things: [{ id: 1 }, { id: 2 }],
43
- meta: { total: 500 }
44
- }
38
+ For example, to display 5 results per page and view the second page of a
39
+ `GET` to `/networks`, your final request would be `GET /networks?....page=2&per_page=5`.
45
40
  ```
46
41
 
47
42
  ## Sideloading
@@ -149,6 +144,7 @@ require 'vericred_client/models/plan_county'
149
144
  require 'vericred_client/models/plan_county_bulk'
150
145
  require 'vericred_client/models/plan_search_response'
151
146
  require 'vericred_client/models/plan_search_result'
147
+ require 'vericred_client/models/plan_zip_county'
152
148
  require 'vericred_client/models/pricing'
153
149
  require 'vericred_client/models/provider'
154
150
  require 'vericred_client/models/provider_show_response'
@@ -31,17 +31,12 @@ The current version is `v3`. Previous versions are `v1` and `v2`.
31
31
 
32
32
  ## Pagination
33
33
 
34
- Most endpoints are not paginated. It will be noted in the documentation if/when
35
- an endpoint is paginated.
34
+ Endpoints that accept `page` and `per_page` parameters are paginated. They expose
35
+ four additional fields that contain data about your position in the response,
36
+ namely `Total`, `Per-Page`, `Link`, and `Page` as described in [RFC-5988](https://tools.ietf.org/html/rfc5988).
36
37
 
37
- When pagination is present, a `meta` stanza will be present in the response
38
- with the total number of records
39
-
40
- ```
41
- {
42
- things: [{ id: 1 }, { id: 2 }],
43
- meta: { total: 500 }
44
- }
38
+ For example, to display 5 results per page and view the second page of a
39
+ `GET` to `/networks`, your final request would be `GET /networks?....page=2&per_page=5`.
45
40
  ```
46
41
 
47
42
  ## Sideloading
@@ -154,7 +149,6 @@ returns all DrugCoverages for a given Drug
154
149
  # @param audience Two-character state code
155
150
  # @param state_code Two-character state code
156
151
  # @param [Hash] opts the optional parameters
157
- # @option opts [String] :vericred_api_key API Key
158
152
  # @return [DrugCoverageResponse]
159
153
  describe 'get_drug_coverages test' do
160
154
  it "should work" do
@@ -171,7 +165,6 @@ returns all DrugCoverages for a given Drug
171
165
  # Search for drugs by proprietary name
172
166
  # @param search_term Full or partial proprietary name of drug
173
167
  # @param [Hash] opts the optional parameters
174
- # @option opts [String] :vericred_api_key API Key
175
168
  # @return [DrugSearchResponse]
176
169
  describe 'list_drugs test' do
177
170
  it "should work" do
@@ -31,17 +31,12 @@ The current version is `v3`. Previous versions are `v1` and `v2`.
31
31
 
32
32
  ## Pagination
33
33
 
34
- Most endpoints are not paginated. It will be noted in the documentation if/when
35
- an endpoint is paginated.
34
+ Endpoints that accept `page` and `per_page` parameters are paginated. They expose
35
+ four additional fields that contain data about your position in the response,
36
+ namely `Total`, `Per-Page`, `Link`, and `Page` as described in [RFC-5988](https://tools.ietf.org/html/rfc5988).
36
37
 
37
- When pagination is present, a `meta` stanza will be present in the response
38
- with the total number of records
39
-
40
- ```
41
- {
42
- things: [{ id: 1 }, { id: 2 }],
43
- meta: { total: 500 }
44
- }
38
+ For example, to display 5 results per page and view the second page of a
39
+ `GET` to `/networks`, your final request would be `GET /networks?....page=2&per_page=5`.
45
40
  ```
46
41
 
47
42
  ## Sideloading
@@ -149,9 +144,11 @@ describe 'NetworksApi' do
149
144
  # Networks
150
145
  # A network is a list of the doctors, other health care providers,
151
146
  and hospitals that a plan has contracted with to provide medical care to
152
- its members.
147
+ its members. This endpoint is paginated.
153
148
  # @param carrier_id Carrier HIOS Issuer ID
154
149
  # @param [Hash] opts the optional parameters
150
+ # @option opts [Integer] :page Page of paginated response
151
+ # @option opts [Integer] :per_page Responses per page
155
152
  # @return [NetworkSearchResponse]
156
153
  describe 'list_networks test' do
157
154
  it "should work" do
@@ -31,17 +31,12 @@ The current version is `v3`. Previous versions are `v1` and `v2`.
31
31
 
32
32
  ## Pagination
33
33
 
34
- Most endpoints are not paginated. It will be noted in the documentation if/when
35
- an endpoint is paginated.
34
+ Endpoints that accept `page` and `per_page` parameters are paginated. They expose
35
+ four additional fields that contain data about your position in the response,
36
+ namely `Total`, `Per-Page`, `Link`, and `Page` as described in [RFC-5988](https://tools.ietf.org/html/rfc5988).
36
37
 
37
- When pagination is present, a `meta` stanza will be present in the response
38
- with the total number of records
39
-
40
- ```
41
- {
42
- things: [{ id: 1 }, { id: 2 }],
43
- meta: { total: 500 }
44
- }
38
+ For example, to display 5 results per page and view the second page of a
39
+ `GET` to `/networks`, your final request would be `GET /networks?....page=2&per_page=5`.
45
40
  ```
46
41
 
47
42
  ## Sideloading
@@ -151,7 +146,7 @@ describe 'PlansApi' do
151
146
 
152
147
  Searching for a set of plans requires a `zip_code` and `fips_code`
153
148
  code. These are used to determine pricing and availabity
154
- of health plans.
149
+ of health plans. This endpoint is paginated.
155
150
 
156
151
  Optionally, you may provide a list of Applicants or Providers
157
152
 
@@ -208,6 +203,14 @@ and return it for each plan. If no values are provided, the
208
203
 
209
204
  `GET /plans?zip_code=07451&fips_code=33025&household_size=4&household_income=40000`
210
205
 
206
+
207
+ ### Sorting
208
+
209
+ Plans can be sorted by the `premium`, `carrier_name`, `level`, and `plan_type` fields,
210
+ by either ascending (as `asc`) or descending (as `dsc) sort under the `sort` field.
211
+
212
+ For example, to sort plans by level, the sort parameter would be `level:asc`.
213
+
211
214
  # @param [Hash] opts the optional parameters
212
215
  # @option opts [RequestPlanFind] :body
213
216
  # @return [PlanSearchResponse]
@@ -31,17 +31,12 @@ The current version is `v3`. Previous versions are `v1` and `v2`.
31
31
 
32
32
  ## Pagination
33
33
 
34
- Most endpoints are not paginated. It will be noted in the documentation if/when
35
- an endpoint is paginated.
34
+ Endpoints that accept `page` and `per_page` parameters are paginated. They expose
35
+ four additional fields that contain data about your position in the response,
36
+ namely `Total`, `Per-Page`, `Link`, and `Page` as described in [RFC-5988](https://tools.ietf.org/html/rfc5988).
36
37
 
37
- When pagination is present, a `meta` stanza will be present in the response
38
- with the total number of records
39
-
40
- ```
41
- {
42
- things: [{ id: 1 }, { id: 2 }],
43
- meta: { total: 500 }
44
- }
38
+ For example, to display 5 results per page and view the second page of a
39
+ `GET` to `/networks`, your final request would be `GET /networks?....page=2&per_page=5`.
45
40
  ```
46
41
 
47
42
  ## Sideloading
@@ -150,7 +145,6 @@ describe 'ProvidersApi' do
150
145
  # To retrieve a specific provider, just perform a GET using his NPI number
151
146
  # @param npi NPI number
152
147
  # @param [Hash] opts the optional parameters
153
- # @option opts [String] :vericred_api_key API Key
154
148
  # @return [ProviderShowResponse]
155
149
  describe 'get_provider test' do
156
150
  it "should work" do
@@ -31,17 +31,12 @@ The current version is `v3`. Previous versions are `v1` and `v2`.
31
31
 
32
32
  ## Pagination
33
33
 
34
- Most endpoints are not paginated. It will be noted in the documentation if/when
35
- an endpoint is paginated.
34
+ Endpoints that accept `page` and `per_page` parameters are paginated. They expose
35
+ four additional fields that contain data about your position in the response,
36
+ namely `Total`, `Per-Page`, `Link`, and `Page` as described in [RFC-5988](https://tools.ietf.org/html/rfc5988).
36
37
 
37
- When pagination is present, a `meta` stanza will be present in the response
38
- with the total number of records
39
-
40
- ```
41
- {
42
- things: [{ id: 1 }, { id: 2 }],
43
- meta: { total: 500 }
44
- }
38
+ For example, to display 5 results per page and view the second page of a
39
+ `GET` to `/networks`, your final request would be `GET /networks?....page=2&per_page=5`.
45
40
  ```
46
41
 
47
42
  ## Sideloading
@@ -150,7 +145,6 @@ describe 'ZipCountiesApi' do
150
145
  # Our `Plan` endpoints require a zip code and a fips (county) code. This is because plan pricing requires both of these elements. Users are unlikely to know their fips code, so we provide this endpoint to look up a `ZipCounty` by zip code and return both the selected zip and fips codes.
151
146
  # @param zip_prefix Partial five-digit Zip
152
147
  # @param [Hash] opts the optional parameters
153
- # @option opts [String] :vericred_api_key API Key
154
148
  # @return [ZipCountyResponse]
155
149
  describe 'get_zip_counties test' do
156
150
  it "should work" do
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: vericred_client
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.0.6
4
+ version: 0.0.7
5
5
  platform: ruby
6
6
  authors:
7
7
  - Vericred Inc.
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2016-06-01 00:00:00.000000000 Z
11
+ date: 2016-06-27 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: typhoeus
@@ -219,6 +219,7 @@ files:
219
219
  - docs/PlanCountyBulk.md
220
220
  - docs/PlanSearchResponse.md
221
221
  - docs/PlanSearchResult.md
222
+ - docs/PlanZipCounty.md
222
223
  - docs/PlansApi.md
223
224
  - docs/Pricing.md
224
225
  - docs/Provider.md
@@ -265,6 +266,7 @@ files:
265
266
  - lib/vericred_client/models/plan_county_bulk.rb
266
267
  - lib/vericred_client/models/plan_search_response.rb
267
268
  - lib/vericred_client/models/plan_search_result.rb
269
+ - lib/vericred_client/models/plan_zip_county.rb
268
270
  - lib/vericred_client/models/pricing.rb
269
271
  - lib/vericred_client/models/provider.rb
270
272
  - lib/vericred_client/models/provider_show_response.rb