vericred_client 0.0.1 → 0.0.2
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.
- checksums.yaml +4 -4
- data/README.md +5 -5
- data/docs/County.md +2 -2
- data/docs/DrugCoverageApi.md +0 -6
- data/docs/PlansApi.md +0 -64
- data/docs/ProvidersApi.md +2 -22
- data/docs/ZipCountiesApi.md +0 -9
- data/lib/vericred_client/api/drug_coverage_api.rb +2 -10
- data/lib/vericred_client/api/plans_api.rb +2 -126
- data/lib/vericred_client/api/providers_api.rb +6 -38
- data/lib/vericred_client/api/zip_counties_api.rb +2 -16
- data/lib/vericred_client/models/county.rb +2 -2
- data/lib/vericred_client/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 4c1118700476d532dc34d78643c1030fadb398a2
|
4
|
+
data.tar.gz: 7a09f482a934922eb00663e821c69d7d6374372a
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 5906ffced1740ac780327d282bc438ab31be9f0220590e36e9ae7cc042643a67f10f179d4cb98ef6263040368f5d689f5904fbc3879216a2c1bc71e22e266701
|
7
|
+
data.tar.gz: defa34e64d3ff80144b173f7fa403432a60dfbc1577d37a7955e58a69f502bc688c1fa46f2a088619d4ae333a3708a2d30512ff77cf576e85cf98ec89ef165e5
|
data/README.md
CHANGED
@@ -120,8 +120,8 @@ The response would be
|
|
120
120
|
This SDK is automatically generated by the [Swagger Codegen](https://github.com/swagger-api/swagger-codegen) project:
|
121
121
|
|
122
122
|
- API version:
|
123
|
-
- Package version: 0.0.
|
124
|
-
- Build date: 2016-
|
123
|
+
- Package version: 0.0.2
|
124
|
+
- Build date: 2016-05-09T16:32:47.387-04:00
|
125
125
|
- Build package: class io.swagger.codegen.languages.RubyClientCodegen
|
126
126
|
|
127
127
|
## Installation
|
@@ -137,15 +137,15 @@ gem build vericred_client.gemspec
|
|
137
137
|
Then either install the gem locally:
|
138
138
|
|
139
139
|
```shell
|
140
|
-
gem install ./vericred_client-0.0.
|
140
|
+
gem install ./vericred_client-0.0.2.gem
|
141
141
|
```
|
142
|
-
(for development, run `gem install --dev ./vericred_client-0.0.
|
142
|
+
(for development, run `gem install --dev ./vericred_client-0.0.2.gem` to install the development dependencies)
|
143
143
|
|
144
144
|
or publish the gem to a gem hosting service, e.g. [RubyGems](https://rubygems.org/).
|
145
145
|
|
146
146
|
Finally add this to the Gemfile:
|
147
147
|
|
148
|
-
gem 'vericred_client', '~> 0.0.
|
148
|
+
gem 'vericred_client', '~> 0.0.2'
|
149
149
|
|
150
150
|
### Install from Git
|
151
151
|
|
data/docs/County.md
CHANGED
@@ -9,8 +9,8 @@ Name | Type | Description | Notes
|
|
9
9
|
**state_code** | **String** | Two-character state code | [optional]
|
10
10
|
**state_id** | **Integer** | state relationship | [optional]
|
11
11
|
**state_live** | **BOOLEAN** | Is the state containing this county active for consumers?
|
12
|
-
|
12
|
+
*deprecated in favor of last_date_for_individual | [optional]
|
13
13
|
**state_live_for_business** | **BOOLEAN** | Is the state containing this county active for business?
|
14
|
-
|
14
|
+
*deprecated in favor of last_date_for_shop | [optional]
|
15
15
|
|
16
16
|
|
data/docs/DrugCoverageApi.md
CHANGED
@@ -12,12 +12,6 @@ Method | HTTP request | Description
|
|
12
12
|
|
13
13
|
Find Drug Coverages for a given NDC
|
14
14
|
|
15
|
-
Drug Coverages are the specific tier level, quantity limit, prior authorization
|
16
|
-
and step therapy for a given Drug/Plan combination. This endpoint returns
|
17
|
-
all DrugCoverages for a given Drug
|
18
|
-
|
19
|
-
|
20
|
-
|
21
15
|
### Example
|
22
16
|
```ruby
|
23
17
|
# load the gem
|
data/docs/PlansApi.md
CHANGED
@@ -12,70 +12,6 @@ Method | HTTP request | Description
|
|
12
12
|
|
13
13
|
Find a set of plans for a Zip Code and County
|
14
14
|
|
15
|
-
### Location Information
|
16
|
-
|
17
|
-
Searching for a set of plans requires a `zip_code` and `fips_code`
|
18
|
-
code. These are used to determine pricing and availabity
|
19
|
-
of health plans.
|
20
|
-
|
21
|
-
Optionally, you may provide a list of Applicants or Providers
|
22
|
-
|
23
|
-
### Applicants
|
24
|
-
|
25
|
-
This is a list of people who will be covered by the plan. We
|
26
|
-
use this list to calculate the premium. You must include `age`
|
27
|
-
and can include `smoker`, which also factors into pricing in some
|
28
|
-
states.
|
29
|
-
|
30
|
-
Applicants *must* include an age. If smoker is omitted, its value is assumed
|
31
|
-
to be false.
|
32
|
-
|
33
|
-
#### Multiple Applicants
|
34
|
-
|
35
|
-
To get pricing for multiple applicants, just append multiple sets
|
36
|
-
of data to the URL with the age and smoking status of each applicant
|
37
|
-
next to each other.
|
38
|
-
|
39
|
-
For example, given two applicants - one age 32 and a non-smoker and one
|
40
|
-
age 29 and a smoker, you could use the following request
|
41
|
-
|
42
|
-
`GET /plans?zip_code=07451&fips_code=33025&applicants[][age]=32&applicants[][age]=29&applicants[][smoker]=true`
|
43
|
-
|
44
|
-
It would also be acceptible to include `applicants[][smoker]=false` after the
|
45
|
-
first applicant's age.
|
46
|
-
|
47
|
-
### Providers
|
48
|
-
|
49
|
-
We identify Providers (Doctors) by their National Practitioner
|
50
|
-
Index number (NPI). If you pass a list of Providers, keyed by
|
51
|
-
their NPI number, we will return a list of which Providers are
|
52
|
-
in and out of network for each plan returned.
|
53
|
-
|
54
|
-
For example, if we had two providers with the NPI numbers `12345` and `23456`
|
55
|
-
you would make the following request
|
56
|
-
|
57
|
-
`GET /plans?zip_code=07451&fips_code=33025&providers[][npi]=12345&providers[][npi]=23456`
|
58
|
-
|
59
|
-
### Enrollment Date
|
60
|
-
|
61
|
-
To calculate plan pricing and availability, we default to the current date
|
62
|
-
as the enrollment date. To specify a date in the future (or the past), pass
|
63
|
-
a string with the format `YYYY-MM-DD` in the `enrollment_date` parameter.
|
64
|
-
|
65
|
-
`GET /plans?zip_code=07451&fips_code=33025&enrollment_date=2016-01-01`
|
66
|
-
|
67
|
-
### Subsidy
|
68
|
-
|
69
|
-
On-marketplace plans are eligible for a subsidy based on the
|
70
|
-
`household_size` and `household_income` of the applicants. If you
|
71
|
-
pass those values, we will calculate the `subsidized_premium`
|
72
|
-
and return it for each plan. If no values are provided, the
|
73
|
-
`subsidized_premium` will be the same as the `premium`
|
74
|
-
|
75
|
-
`GET /plans?zip_code=07451&fips_code=33025&household_size=4&household_income=40000`
|
76
|
-
|
77
|
-
|
78
|
-
|
79
15
|
### Example
|
80
16
|
```ruby
|
81
17
|
# load the gem
|
data/docs/ProvidersApi.md
CHANGED
@@ -13,22 +13,6 @@ Method | HTTP request | Description
|
|
13
13
|
|
14
14
|
Find providers by term and zip code
|
15
15
|
|
16
|
-
All `Provider` searches require a `zip_code`, which we use for weighting
|
17
|
-
the search results to favor `Provider`s that are near the user. For example,
|
18
|
-
we would want "Dr. John Smith" who is 5 miles away to appear before
|
19
|
-
"Dr. John Smith" who is 100 miles away.
|
20
|
-
|
21
|
-
The weighting also allows for non-exact matches. In our prior example, we
|
22
|
-
would want "Dr. Jon Smith" who is 2 miles away to appear before the exact
|
23
|
-
match "Dr. John Smith" who is 100 miles away because it is more likely that
|
24
|
-
the user just entered an incorrect name.
|
25
|
-
|
26
|
-
The free text search also supports Specialty name search and "body part"
|
27
|
-
Specialty name search. So, searching "John Smith nose" would return
|
28
|
-
"Dr. John Smith", the ENT Specialist before "Dr. John Smith" the Internist.
|
29
|
-
|
30
|
-
|
31
|
-
|
32
16
|
### Example
|
33
17
|
```ruby
|
34
18
|
# load the gem
|
@@ -41,7 +25,7 @@ search_term = "search_term_example" # String | String to search by
|
|
41
25
|
zip_code = "zip_code_example" # String | Zip Code to search near
|
42
26
|
|
43
27
|
opts = {
|
44
|
-
accepts_insurance: "accepts_insurance_example", # String | Limit results to Providers who accept at least one insurance
|
28
|
+
accepts_insurance: "accepts_insurance_example", # String | Limit results to Providers who accept at least one insurance?
|
45
29
|
hios_ids: ["hios_ids_example"], # Array<String> | HIOS id of one or more plans
|
46
30
|
page: "page_example", # String | Page number
|
47
31
|
per_page: "per_page_example", # String | Number of records to return per page
|
@@ -63,7 +47,7 @@ Name | Type | Description | Notes
|
|
63
47
|
------------- | ------------- | ------------- | -------------
|
64
48
|
**search_term** | **String**| String to search by |
|
65
49
|
**zip_code** | **String**| Zip Code to search near |
|
66
|
-
**accepts_insurance** | **String**| Limit results to Providers who accept at least one insurance
|
50
|
+
**accepts_insurance** | **String**| Limit results to Providers who accept at least one insurance? | [optional]
|
67
51
|
**hios_ids** | [**Array<String>**](String.md)| HIOS id of one or more plans | [optional]
|
68
52
|
**page** | **String**| Page number | [optional]
|
69
53
|
**per_page** | **String**| Number of records to return per page | [optional]
|
@@ -89,10 +73,6 @@ No authorization required
|
|
89
73
|
|
90
74
|
Find a specific Provider
|
91
75
|
|
92
|
-
To retrieve a specific provider, just perform a GET using his NPI number
|
93
|
-
|
94
|
-
|
95
|
-
|
96
76
|
### Example
|
97
77
|
```ruby
|
98
78
|
# load the gem
|
data/docs/ZipCountiesApi.md
CHANGED
@@ -12,15 +12,6 @@ Method | HTTP request | Description
|
|
12
12
|
|
13
13
|
Find Zip Counties by Zip Code
|
14
14
|
|
15
|
-
### Finding Zip Code and Fips Code
|
16
|
-
|
17
|
-
Our `Plan` endpoints require a zip code and a fips (county) code. This is
|
18
|
-
because plan pricing requires both of these elements. Users are unlikely to
|
19
|
-
know their fips code, so we provide this endpoint to look up a `ZipCounty` by
|
20
|
-
zip code and return both the selected zip and fips codes.
|
21
|
-
|
22
|
-
|
23
|
-
|
24
15
|
### Example
|
25
16
|
```ruby
|
26
17
|
# load the gem
|
@@ -134,11 +134,7 @@ module VericredClient
|
|
134
134
|
end
|
135
135
|
|
136
136
|
# Find Drug Coverages for a given NDC
|
137
|
-
#
|
138
|
-
and step therapy for a given Drug/Plan combination. This endpoint returns
|
139
|
-
all DrugCoverages for a given Drug
|
140
|
-
|
141
|
-
|
137
|
+
#
|
142
138
|
# @param ndc NDC for a drug
|
143
139
|
# @param [Hash] opts the optional parameters
|
144
140
|
# @return [Array<DrugCoverage>]
|
@@ -148,11 +144,7 @@ all DrugCoverages for a given Drug
|
|
148
144
|
end
|
149
145
|
|
150
146
|
# Find Drug Coverages for a given NDC
|
151
|
-
#
|
152
|
-
and step therapy for a given Drug/Plan combination. This endpoint returns
|
153
|
-
all DrugCoverages for a given Drug
|
154
|
-
|
155
|
-
|
147
|
+
#
|
156
148
|
# @param ndc NDC for a drug
|
157
149
|
# @param [Hash] opts the optional parameters
|
158
150
|
# @return [Array<(Array<DrugCoverage>, Fixnum, Hash)>] Array<DrugCoverage> data, response status code and response headers
|
@@ -134,69 +134,7 @@ module VericredClient
|
|
134
134
|
end
|
135
135
|
|
136
136
|
# Find a set of plans for a Zip Code and County
|
137
|
-
#
|
138
|
-
|
139
|
-
Searching for a set of plans requires a `zip_code` and `fips_code`
|
140
|
-
code. These are used to determine pricing and availabity
|
141
|
-
of health plans.
|
142
|
-
|
143
|
-
Optionally, you may provide a list of Applicants or Providers
|
144
|
-
|
145
|
-
### Applicants
|
146
|
-
|
147
|
-
This is a list of people who will be covered by the plan. We
|
148
|
-
use this list to calculate the premium. You must include `age`
|
149
|
-
and can include `smoker`, which also factors into pricing in some
|
150
|
-
states.
|
151
|
-
|
152
|
-
Applicants *must* include an age. If smoker is omitted, its value is assumed
|
153
|
-
to be false.
|
154
|
-
|
155
|
-
#### Multiple Applicants
|
156
|
-
|
157
|
-
To get pricing for multiple applicants, just append multiple sets
|
158
|
-
of data to the URL with the age and smoking status of each applicant
|
159
|
-
next to each other.
|
160
|
-
|
161
|
-
For example, given two applicants - one age 32 and a non-smoker and one
|
162
|
-
age 29 and a smoker, you could use the following request
|
163
|
-
|
164
|
-
`GET /plans?zip_code=07451&fips_code=33025&applicants[][age]=32&applicants[][age]=29&applicants[][smoker]=true`
|
165
|
-
|
166
|
-
It would also be acceptible to include `applicants[][smoker]=false` after the
|
167
|
-
first applicant's age.
|
168
|
-
|
169
|
-
### Providers
|
170
|
-
|
171
|
-
We identify Providers (Doctors) by their National Practitioner
|
172
|
-
Index number (NPI). If you pass a list of Providers, keyed by
|
173
|
-
their NPI number, we will return a list of which Providers are
|
174
|
-
in and out of network for each plan returned.
|
175
|
-
|
176
|
-
For example, if we had two providers with the NPI numbers `12345` and `23456`
|
177
|
-
you would make the following request
|
178
|
-
|
179
|
-
`GET /plans?zip_code=07451&fips_code=33025&providers[][npi]=12345&providers[][npi]=23456`
|
180
|
-
|
181
|
-
### Enrollment Date
|
182
|
-
|
183
|
-
To calculate plan pricing and availability, we default to the current date
|
184
|
-
as the enrollment date. To specify a date in the future (or the past), pass
|
185
|
-
a string with the format `YYYY-MM-DD` in the `enrollment_date` parameter.
|
186
|
-
|
187
|
-
`GET /plans?zip_code=07451&fips_code=33025&enrollment_date=2016-01-01`
|
188
|
-
|
189
|
-
### Subsidy
|
190
|
-
|
191
|
-
On-marketplace plans are eligible for a subsidy based on the
|
192
|
-
`household_size` and `household_income` of the applicants. If you
|
193
|
-
pass those values, we will calculate the `subsidized_premium`
|
194
|
-
and return it for each plan. If no values are provided, the
|
195
|
-
`subsidized_premium` will be the same as the `premium`
|
196
|
-
|
197
|
-
`GET /plans?zip_code=07451&fips_code=33025&household_size=4&household_income=40000`
|
198
|
-
|
199
|
-
|
137
|
+
#
|
200
138
|
# @param query Plan query
|
201
139
|
# @param [Hash] opts the optional parameters
|
202
140
|
# @return [Array<Plan>]
|
@@ -206,69 +144,7 @@ and return it for each plan. If no values are provided, the
|
|
206
144
|
end
|
207
145
|
|
208
146
|
# Find a set of plans for a Zip Code and County
|
209
|
-
#
|
210
|
-
|
211
|
-
Searching for a set of plans requires a `zip_code` and `fips_code`
|
212
|
-
code. These are used to determine pricing and availabity
|
213
|
-
of health plans.
|
214
|
-
|
215
|
-
Optionally, you may provide a list of Applicants or Providers
|
216
|
-
|
217
|
-
### Applicants
|
218
|
-
|
219
|
-
This is a list of people who will be covered by the plan. We
|
220
|
-
use this list to calculate the premium. You must include `age`
|
221
|
-
and can include `smoker`, which also factors into pricing in some
|
222
|
-
states.
|
223
|
-
|
224
|
-
Applicants *must* include an age. If smoker is omitted, its value is assumed
|
225
|
-
to be false.
|
226
|
-
|
227
|
-
#### Multiple Applicants
|
228
|
-
|
229
|
-
To get pricing for multiple applicants, just append multiple sets
|
230
|
-
of data to the URL with the age and smoking status of each applicant
|
231
|
-
next to each other.
|
232
|
-
|
233
|
-
For example, given two applicants - one age 32 and a non-smoker and one
|
234
|
-
age 29 and a smoker, you could use the following request
|
235
|
-
|
236
|
-
`GET /plans?zip_code=07451&fips_code=33025&applicants[][age]=32&applicants[][age]=29&applicants[][smoker]=true`
|
237
|
-
|
238
|
-
It would also be acceptible to include `applicants[][smoker]=false` after the
|
239
|
-
first applicant's age.
|
240
|
-
|
241
|
-
### Providers
|
242
|
-
|
243
|
-
We identify Providers (Doctors) by their National Practitioner
|
244
|
-
Index number (NPI). If you pass a list of Providers, keyed by
|
245
|
-
their NPI number, we will return a list of which Providers are
|
246
|
-
in and out of network for each plan returned.
|
247
|
-
|
248
|
-
For example, if we had two providers with the NPI numbers `12345` and `23456`
|
249
|
-
you would make the following request
|
250
|
-
|
251
|
-
`GET /plans?zip_code=07451&fips_code=33025&providers[][npi]=12345&providers[][npi]=23456`
|
252
|
-
|
253
|
-
### Enrollment Date
|
254
|
-
|
255
|
-
To calculate plan pricing and availability, we default to the current date
|
256
|
-
as the enrollment date. To specify a date in the future (or the past), pass
|
257
|
-
a string with the format `YYYY-MM-DD` in the `enrollment_date` parameter.
|
258
|
-
|
259
|
-
`GET /plans?zip_code=07451&fips_code=33025&enrollment_date=2016-01-01`
|
260
|
-
|
261
|
-
### Subsidy
|
262
|
-
|
263
|
-
On-marketplace plans are eligible for a subsidy based on the
|
264
|
-
`household_size` and `household_income` of the applicants. If you
|
265
|
-
pass those values, we will calculate the `subsidized_premium`
|
266
|
-
and return it for each plan. If no values are provided, the
|
267
|
-
`subsidized_premium` will be the same as the `premium`
|
268
|
-
|
269
|
-
`GET /plans?zip_code=07451&fips_code=33025&household_size=4&household_income=40000`
|
270
|
-
|
271
|
-
|
147
|
+
#
|
272
148
|
# @param query Plan query
|
273
149
|
# @param [Hash] opts the optional parameters
|
274
150
|
# @return [Array<(Array<Plan>, Fixnum, Hash)>] Array<Plan> data, response status code and response headers
|
@@ -134,25 +134,11 @@ module VericredClient
|
|
134
134
|
end
|
135
135
|
|
136
136
|
# Find providers by term and zip code
|
137
|
-
#
|
138
|
-
the search results to favor `Provider`s that are near the user. For example,
|
139
|
-
we would want "Dr. John Smith" who is 5 miles away to appear before
|
140
|
-
"Dr. John Smith" who is 100 miles away.
|
141
|
-
|
142
|
-
The weighting also allows for non-exact matches. In our prior example, we
|
143
|
-
would want "Dr. Jon Smith" who is 2 miles away to appear before the exact
|
144
|
-
match "Dr. John Smith" who is 100 miles away because it is more likely that
|
145
|
-
the user just entered an incorrect name.
|
146
|
-
|
147
|
-
The free text search also supports Specialty name search and "body part"
|
148
|
-
Specialty name search. So, searching "John Smith nose" would return
|
149
|
-
"Dr. John Smith", the ENT Specialist before "Dr. John Smith" the Internist.
|
150
|
-
|
151
|
-
|
137
|
+
#
|
152
138
|
# @param search_term String to search by
|
153
139
|
# @param zip_code Zip Code to search near
|
154
140
|
# @param [Hash] opts the optional parameters
|
155
|
-
# @option opts [String] :accepts_insurance Limit results to Providers who accept at least one insurance
|
141
|
+
# @option opts [String] :accepts_insurance Limit results to Providers who accept at least one insurance?
|
156
142
|
# @option opts [Array<String>] :hios_ids HIOS id of one or more plans
|
157
143
|
# @option opts [String] :page Page number
|
158
144
|
# @option opts [String] :per_page Number of records to return per page
|
@@ -164,25 +150,11 @@ Specialty name search. So, searching "John Smith nose" would return
|
|
164
150
|
end
|
165
151
|
|
166
152
|
# Find providers by term and zip code
|
167
|
-
#
|
168
|
-
the search results to favor `Provider`s that are near the user. For example,
|
169
|
-
we would want "Dr. John Smith" who is 5 miles away to appear before
|
170
|
-
"Dr. John Smith" who is 100 miles away.
|
171
|
-
|
172
|
-
The weighting also allows for non-exact matches. In our prior example, we
|
173
|
-
would want "Dr. Jon Smith" who is 2 miles away to appear before the exact
|
174
|
-
match "Dr. John Smith" who is 100 miles away because it is more likely that
|
175
|
-
the user just entered an incorrect name.
|
176
|
-
|
177
|
-
The free text search also supports Specialty name search and "body part"
|
178
|
-
Specialty name search. So, searching "John Smith nose" would return
|
179
|
-
"Dr. John Smith", the ENT Specialist before "Dr. John Smith" the Internist.
|
180
|
-
|
181
|
-
|
153
|
+
#
|
182
154
|
# @param search_term String to search by
|
183
155
|
# @param zip_code Zip Code to search near
|
184
156
|
# @param [Hash] opts the optional parameters
|
185
|
-
# @option opts [String] :accepts_insurance Limit results to Providers who accept at least one insurance
|
157
|
+
# @option opts [String] :accepts_insurance Limit results to Providers who accept at least one insurance?
|
186
158
|
# @option opts [Array<String>] :hios_ids HIOS id of one or more plans
|
187
159
|
# @option opts [String] :page Page number
|
188
160
|
# @option opts [String] :per_page Number of records to return per page
|
@@ -240,9 +212,7 @@ Specialty name search. So, searching "John Smith nose" would return
|
|
240
212
|
end
|
241
213
|
|
242
214
|
# Find a specific Provider
|
243
|
-
#
|
244
|
-
|
245
|
-
|
215
|
+
#
|
246
216
|
# @param npi NPI number
|
247
217
|
# @param [Hash] opts the optional parameters
|
248
218
|
# @return [InlineResponse2001]
|
@@ -252,9 +222,7 @@ Specialty name search. So, searching "John Smith nose" would return
|
|
252
222
|
end
|
253
223
|
|
254
224
|
# Find a specific Provider
|
255
|
-
#
|
256
|
-
|
257
|
-
|
225
|
+
#
|
258
226
|
# @param npi NPI number
|
259
227
|
# @param [Hash] opts the optional parameters
|
260
228
|
# @return [Array<(InlineResponse2001, Fixnum, Hash)>] InlineResponse2001 data, response status code and response headers
|
@@ -134,14 +134,7 @@ module VericredClient
|
|
134
134
|
end
|
135
135
|
|
136
136
|
# Find Zip Counties by Zip Code
|
137
|
-
#
|
138
|
-
|
139
|
-
Our `Plan` endpoints require a zip code and a fips (county) code. This is
|
140
|
-
because plan pricing requires both of these elements. Users are unlikely to
|
141
|
-
know their fips code, so we provide this endpoint to look up a `ZipCounty` by
|
142
|
-
zip code and return both the selected zip and fips codes.
|
143
|
-
|
144
|
-
|
137
|
+
#
|
145
138
|
# @param zip_prefix Partial five-digit Zip
|
146
139
|
# @param [Hash] opts the optional parameters
|
147
140
|
# @return [InlineResponse2002]
|
@@ -151,14 +144,7 @@ zip code and return both the selected zip and fips codes.
|
|
151
144
|
end
|
152
145
|
|
153
146
|
# Find Zip Counties by Zip Code
|
154
|
-
#
|
155
|
-
|
156
|
-
Our `Plan` endpoints require a zip code and a fips (county) code. This is
|
157
|
-
because plan pricing requires both of these elements. Users are unlikely to
|
158
|
-
know their fips code, so we provide this endpoint to look up a `ZipCounty` by
|
159
|
-
zip code and return both the selected zip and fips codes.
|
160
|
-
|
161
|
-
|
147
|
+
#
|
162
148
|
# @param zip_prefix Partial five-digit Zip
|
163
149
|
# @param [Hash] opts the optional parameters
|
164
150
|
# @return [Array<(InlineResponse2002, Fixnum, Hash)>] InlineResponse2002 data, response status code and response headers
|
@@ -143,11 +143,11 @@ module VericredClient
|
|
143
143
|
attr_accessor :state_id
|
144
144
|
|
145
145
|
# Is the state containing this county active for consumers?
|
146
|
-
|
146
|
+
*deprecated in favor of last_date_for_individual
|
147
147
|
attr_accessor :state_live
|
148
148
|
|
149
149
|
# Is the state containing this county active for business?
|
150
|
-
|
150
|
+
*deprecated in favor of last_date_for_shop
|
151
151
|
attr_accessor :state_live_for_business
|
152
152
|
|
153
153
|
# Attribute mapping from ruby-style variable name to JSON key.
|
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.
|
4
|
+
version: 0.0.2
|
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-
|
11
|
+
date: 2016-05-09 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: typhoeus
|