vericred_client 0.0.25 → 0.0.27

data/lib/vericred_client/api/providers_api.rb

@@ -23,16 +23,18 @@ which we make available for several common programming languages.
 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"`
+`curl -H 'Vericred-Api-Key: YOUR_KEY' "https://api.vericred.com/drugs?search_term=Lipitor"`
 
 ## 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 `v4`.  We also support `v2` and `v3`
+The current version is `v6`.  We support prior versions. Our latest
+stable version is `v7` and we will indicate in the documentation for an
+endpoint if it's required.
 
-`curl -H 'Vericred-Api-Key: YOUR_KEY' -H 'Accept-Version: v3' "https://api.vericred.com/providers?search_term=Foo&zip_code=11215"`
+`curl -H 'Vericred-Api-Key: YOUR_KEY' -H 'Accept-Version: v6' "https://api.vericred.com/drugs?search_term=Lipitor"`
 
 ## Pagination
 
@@ -95,14 +97,14 @@ We also want the `name` and `code` from the `states` key, so we would
 add the parameters `select=states.name,states.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`
+Our final request would be `GET /providers/1234567898?select=provider.name,provider.phone,states.name,states.code`
 
 The response would be
 
 ```
 {
   provider: {
-    id: 1,
+    id: 1234567898,
     name: 'John',
     phone: '1234567890'
   },
@@ -333,6 +335,16 @@ The following are the supported Benefit Fields for Vision:
 - laser\_vision\_correction
 - additional\_pairs\_of\_eyeglasses
 
+### Medicare Advantage
+
+Medicare Advantage endpoints support MA (Medicare Advantage plans without prescription drug benefits), MAPD (Medicare Advantage plans with prescription drug benefits), and PDP (prescription drug benefits only) plans.
+
+Medical and hospital benefits - we support over 4000 individual plans through our API nationwide. At this time, we do not support EGHP (employer group health plans).
+
+Prescription drug benefits - drug benefits are categorized into initial coverage phase, coverage gap phase, and catastrophic phase. Each phase is broken down by drug tiers, pharmacy tiers, and length of supply.
+
+[Click here](#header-medicare-advantage-quotes) to learn more about quoting Medicare Advantage plans.
+
 ## Rates
 
 Rates are returned from the API as a part of [Quoting](#header-quoting).  We calculate Rates in one of two ways.
@@ -614,6 +626,19 @@ Note that in contrast to [Major Medical Quotes](#majormedicalquotes), [Vision Qu
 
 Also note that [Subsidies](#subsidies) and [Cost Sharing Reduction](#costsharingreductionplans) are *not* relevant for [Vision Quotes](#visionquotes).
 
+### Medicare Advantage quotes
+
+Given an enrollment date and location, you can search all plans available at this location using [/plans/medadv/search](#medicare-advantage-plans-medicare-advantage-plans-post); you can also search a specific plan using its plan ID with [/plans/medadv/{plan_id}](#medicare-advantage-plans-medicare-advantage-plans-get) if the plan ID is already known. The following example contains the required parameters:
+```
+{
+"zip_code": "02880",
+"fips_code": "44009",
+"enrollment_date": "2019-01-01"
+}
+```
+To view the technical documentation, [click here](#medicare-advantage-plans).
+
+
 ## Quotes for Groups
 A Group Quote finds [Plans](#header-plans) and [Rates](#header-rates) for a group of employees for a small business.  Different [Plans](#header-plans) are available to small groups than are available in [Individual Quoting](#individualquotes).  In addition, [Business Rules](#header-business-rules) that apply across multiple families or based upon employer attributes such as [SIC](https://en.wikipedia.org/wiki/Standard_Industrial_Classification) code factor into rates and availability.
 
@@ -1022,8 +1047,78 @@ module VericredClient
       return data, status_code, headers
     end
 
+    # Provider Plans
+    # Retrieve the plans a provider accepts.  **New Verison:** In order to use this endpoint, please set your version header to `v7`. If you are using previous versions and want to get the list of `plan_ids` that a provider accepts, you can use the `hios_ids` key in the Provider Show `GET /providers/:npi` endpoint.  #### External Id Types   Plan `external_ids` are returned as a list, with each item containing   both a `type` and a `value`. Below is a list of possible types:    | Type           | Description                                                                                                                                          |   | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |   | hios_id        | The HIOS ID of the plan. This type will be returned for under-65 ACA medical plans.                                                                  |   | contract_id    | A contract identifier for the plan. This will be returned for all Medicare Advantage plans and any other plan that contains external contract ids.   |   | package_code   | A package code for the plan. This value will be returned if there is a package in which the plan is bundled.                                        |
+    # @param npi NPI number
+    # @param line_of_coverage The line of coverage the plans are in. Options are `medical`, `medicare_advantage`, `dental`, or `vision`.
+    # @param year The year the plans are effective in.
+    # @param [Hash] opts the optional parameters
+    # @option opts [String] :market The market the plans are for. Options are `individual`, `small_group`, `large_group`.
+    # @return [ProviderPlans]
+    def get_provider_plans(npi, line_of_coverage, year, opts = {})
+      data, _status_code, _headers = get_provider_plans_with_http_info(npi, line_of_coverage, year, opts)
+      return data
+    end
+
+    # Provider Plans
+    # Retrieve the plans a provider accepts.  **New Verison:** In order to use this endpoint, please set your version header to `v7`. If you are using previous versions and want to get the list of `plan_ids` that a provider accepts, you can use the `hios_ids` key in the Provider Show `GET /providers/:npi` endpoint.  #### External Id Types   Plan `external_ids` are returned as a list, with each item containing   both a `type` and a `value`. Below is a list of possible types:    | Type           | Description                                                                                                                                          |   | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |   | hios_id        | The HIOS ID of the plan. This type will be returned for under-65 ACA medical plans.                                                                  |   | contract_id    | A contract identifier for the plan. This will be returned for all Medicare Advantage plans and any other plan that contains external contract ids.   |   | package_code   | A package code for the plan. This value will be returned if there is a package in which the plan is bundled.                                        |
+    # @param npi NPI number
+    # @param line_of_coverage The line of coverage the plans are in. Options are `medical`, `medicare_advantage`, `dental`, or `vision`.
+    # @param year The year the plans are effective in.
+    # @param [Hash] opts the optional parameters
+    # @option opts [String] :market The market the plans are for. Options are `individual`, `small_group`, `large_group`.
+    # @return [Array<(ProviderPlans, Fixnum, Hash)>] ProviderPlans data, response status code and response headers
+    def get_provider_plans_with_http_info(npi, line_of_coverage, year, opts = {})
+      if @api_client.config.debugging
+        @api_client.config.logger.debug "Calling API: ProvidersApi.get_provider_plans ..."
+      end
+      # verify the required parameter 'npi' is set
+      fail ArgumentError, "Missing the required parameter 'npi' when calling ProvidersApi.get_provider_plans" if npi.nil?
+      # verify the required parameter 'line_of_coverage' is set
+      fail ArgumentError, "Missing the required parameter 'line_of_coverage' when calling ProvidersApi.get_provider_plans" if line_of_coverage.nil?
+      # verify the required parameter 'year' is set
+      fail ArgumentError, "Missing the required parameter 'year' when calling ProvidersApi.get_provider_plans" if year.nil?
+      # resource path
+      local_var_path = "/providers/{npi}/plans".sub('{format}','json').sub('{' + 'npi' + '}', npi.to_s)
+
+      # query parameters
+      query_params = {}
+      query_params[:'line_of_coverage'] = line_of_coverage
+      query_params[:'year'] = year
+      query_params[:'market'] = opts[:'market'] if !opts[:'market'].nil?
+
+      # header parameters
+      header_params = {}
+
+      # HTTP header 'Accept' (if needed)
+      local_header_accept = []
+      local_header_accept_result = @api_client.select_header_accept(local_header_accept) and header_params['Accept'] = local_header_accept_result
+
+      # HTTP header 'Content-Type'
+      local_header_content_type = []
+      header_params['Content-Type'] = @api_client.select_header_content_type(local_header_content_type)
+
+      # form parameters
+      form_params = {}
+
+      # http body (model)
+      post_body = nil
+      auth_names = ['Vericred-Api-Key']
+      data, status_code, headers = @api_client.call_api(:GET, local_var_path,
+        :header_params => header_params,
+        :query_params => query_params,
+        :form_params => form_params,
+        :body => post_body,
+        :auth_names => auth_names,
+        :return_type => 'ProviderPlans')
+      if @api_client.config.debugging
+        @api_client.config.logger.debug "API called: ProvidersApi#get_provider_plans\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
+      end
+      return data, status_code, headers
+    end
+
     # Find Providers
-    # ### Provider Details All searches can take a `search_term`, which is used as a component in the score (and thus the ranking/order) of the results.  This is combined with the proximity to the location in ranking results. For example, we would want \"Dr. John Smith\" who is 5 miles away from a given Zip Code to appear before \"Dr. John Smith\" who is 100 miles away.  The weighting also allows for non-exact matches.  In our prior example, we would want \"Dr. Jon Smith\" who is 2 miles away to appear before the exact match \"Dr. John Smith\" who is 100 miles away because it is more likely that the user just entered an incorrect name.  The free text search also supports Specialty name search and \"body part\" Specialty name search.  So, searching \"John Smith nose\" would return \"Dr. John Smith\", the ENT Specialist before \"Dr. John Smith\" the Internist.  In addition, we can filter `Providers` by whether or not they accept *any* insurance.  Our data set includes over 4 million `Providers`, some of whom do not accept any insurance at all.  This filter makes it more likely that the user will find his or her practitioner in some cases.  ### Location Information  All `Provider` searches that do *not* specify `plan_ids` or `network_ids`require some type of location information. We use this information either to weight results or to filter results, depending on the type.  #### Zip Code When providing the `zip_code` parameter, we order the `Providers` returned based on their score, which incorporates their proximity to the given Zip Code and the closeness of match to the search text.  If a `radius` is also provided, we filter out `Providers` who are outside of that radius from the center of the Zip Code provided.  #### Polygon When providing the `polygon` parameter, we filter providers who are outside the bounds of the shape provided.  This is mutually exclusive with `zip_code` and `radius`.  ### Plan/Network Information We can also filter based on `Plan` and `Network` participation, using `plan_ids` and `network_ids`, respectively.  These filters are mutually exclusive and return the union of the resulting sets for each `Plan` or `Network`.  I.e. if you provider Plan A and Plan B, you will receive `Providers` who accept *either* `Plan`.  The same is true for `Networks`. The plan identifiers filter supports both HIOS IDs and contract codes.  ### Examples  *Find Dr. Foo near Brooklyn*  `{ \"search_term\": \"Foo\", \"zip_code\": \"11215\" }`  *Find all Providers within 5 miles of Brooklyn who accept a Plan*  `{ \"zip_code\": \"11215\", \"radius\": 5, \"plan_ids\": [\"88582NY0230001\"] }`  *Find all providers on a map of Brooklyn ordered by a combination of proximity to the center point of the map and relevance to the search term \"ENT\"*  ``` {   \"polygon\": [       {\"lon\":-74.0126609802,\"lat\":40.6275684851 },       {\"lon\":-74.0126609802,\"lat\":40.7097269508 },       {\"lon\":-73.9367866516,\"lat\":40.7097269508 },       {\"lon\":-73.9367866516,\"lat\":40.6275684851 }   ],   \"search_term\" : \"ENT\" } ``` 
+    # ### Provider Details All searches can take a `search_term`, which is used as a component in the score (and thus the ranking/order) of the results.  This is combined with the proximity to the location in ranking results. For example, we would want \"Dr. John Smith\" who is 5 miles away from a given Zip Code to appear before \"Dr. John Smith\" who is 100 miles away.  The weighting also allows for non-exact matches.  In our prior example, we would want \"Dr. Jon Smith\" who is 2 miles away to appear before the exact match \"Dr. John Smith\" who is 100 miles away because it is more likely that the user just entered an incorrect name.  The free text search also supports Specialty name search and \"body part\" Specialty name search.  So, searching \"John Smith nose\" would return \"Dr. John Smith\", the ENT Specialist before \"Dr. John Smith\" the Internist.  In addition, we can filter `Providers` by whether or not they accept *any* insurance.  Our data set includes over 4 million `Providers`, some of whom do not accept any insurance at all.  This filter makes it more likely that the user will find his or her practitioner in some cases.  ### Location Information  All `Provider` searches that do *not* specify `plan_ids` or `network_ids`require some type of location information. We use this information either to weight results or to filter results, depending on the type.  #### Zip Code When providing the `zip_code` parameter, we order the `Providers` returned based on their score, which incorporates their proximity to the given Zip Code and the closeness of match to the search text.  If a `radius` is also provided, we filter out `Providers` who are outside of that radius from the center of the Zip Code provided.  #### Polygon When providing the `polygon` parameter, we filter providers who are outside the bounds of the shape provided.  This is mutually exclusive with `zip_code` and `radius`.  ### Specialty When providing the `specialty_ids` parameter, we filter providers to those who practice those specialties. To find the specialty_ids, please use the [Specialty Search](#specialtes-specialtes-get) endpoint.  ### Plan/Network Information We can also filter based on `Plan` and `Network` participation, using `plan_ids` and `network_ids`, respectively.  These filters are mutually exclusive and return the union of the resulting sets for each `Plan` or `Network`.  I.e. if you provider Plan A and Plan B, you will receive `Providers` who accept *either* `Plan`.  The same is true for `Networks`. The plan identifiers filter supports: Vericred plan IDs returned from the [Dental](#header-dental-quotes) and [Vision](#header-vision-quotes) endpoints, as well as, HIOS IDs and Medicare contract codes.  ### Examples  *Find Dr. Foo near Brooklyn*  `{ \"search_term\": \"Foo\", \"zip_code\": \"11215\" }`  *Find all Providers within 5 miles of Brooklyn who accept a Plan*  `{ \"zip_code\": \"11215\", \"radius\": 5, \"plan_ids\": [\"88582NY0230001\"] }`  *Find all providers on a map of Brooklyn ordered by a combination of proximity to the center point of the map and relevance to the search term \"ENT\"*  ``` {   \"polygon\": [       {\"lon\":-74.0126609802,\"lat\":40.6275684851 },       {\"lon\":-74.0126609802,\"lat\":40.7097269508 },       {\"lon\":-73.9367866516,\"lat\":40.7097269508 },       {\"lon\":-73.9367866516,\"lat\":40.6275684851 }   ],   \"search_term\" : \"ENT\" } ``` 
     # @param body 
     # @param [Hash] opts the optional parameters
     # @return [ProvidersSearchResponse]
@@ -1033,7 +1128,7 @@ module VericredClient
     end
 
     # Find Providers
-    # ### Provider Details All searches can take a &#x60;search_term&#x60;, which is used as a component in the score (and thus the ranking/order) of the results.  This is combined with the proximity to the location in ranking results. For example, we would want \&quot;Dr. John Smith\&quot; who is 5 miles away from a given Zip Code to appear before \&quot;Dr. John Smith\&quot; who is 100 miles away.  The weighting also allows for non-exact matches.  In our prior example, we would want \&quot;Dr. Jon Smith\&quot; who is 2 miles away to appear before the exact match \&quot;Dr. John Smith\&quot; who is 100 miles away because it is more likely that the user just entered an incorrect name.  The free text search also supports Specialty name search and \&quot;body part\&quot; Specialty name search.  So, searching \&quot;John Smith nose\&quot; would return \&quot;Dr. John Smith\&quot;, the ENT Specialist before \&quot;Dr. John Smith\&quot; the Internist.  In addition, we can filter &#x60;Providers&#x60; by whether or not they accept *any* insurance.  Our data set includes over 4 million &#x60;Providers&#x60;, some of whom do not accept any insurance at all.  This filter makes it more likely that the user will find his or her practitioner in some cases.  ### Location Information  All &#x60;Provider&#x60; searches that do *not* specify &#x60;plan_ids&#x60; or &#x60;network_ids&#x60;require some type of location information. We use this information either to weight results or to filter results, depending on the type.  #### Zip Code When providing the &#x60;zip_code&#x60; parameter, we order the &#x60;Providers&#x60; returned based on their score, which incorporates their proximity to the given Zip Code and the closeness of match to the search text.  If a &#x60;radius&#x60; is also provided, we filter out &#x60;Providers&#x60; who are outside of that radius from the center of the Zip Code provided.  #### Polygon When providing the &#x60;polygon&#x60; parameter, we filter providers who are outside the bounds of the shape provided.  This is mutually exclusive with &#x60;zip_code&#x60; and &#x60;radius&#x60;.  ### Plan/Network Information We can also filter based on &#x60;Plan&#x60; and &#x60;Network&#x60; participation, using &#x60;plan_ids&#x60; and &#x60;network_ids&#x60;, respectively.  These filters are mutually exclusive and return the union of the resulting sets for each &#x60;Plan&#x60; or &#x60;Network&#x60;.  I.e. if you provider Plan A and Plan B, you will receive &#x60;Providers&#x60; who accept *either* &#x60;Plan&#x60;.  The same is true for &#x60;Networks&#x60;. The plan identifiers filter supports both HIOS IDs and contract codes.  ### Examples  *Find Dr. Foo near Brooklyn*  &#x60;{ \&quot;search_term\&quot;: \&quot;Foo\&quot;, \&quot;zip_code\&quot;: \&quot;11215\&quot; }&#x60;  *Find all Providers within 5 miles of Brooklyn who accept a Plan*  &#x60;{ \&quot;zip_code\&quot;: \&quot;11215\&quot;, \&quot;radius\&quot;: 5, \&quot;plan_ids\&quot;: [\&quot;88582NY0230001\&quot;] }&#x60;  *Find all providers on a map of Brooklyn ordered by a combination of proximity to the center point of the map and relevance to the search term \&quot;ENT\&quot;*  &#x60;&#x60;&#x60; {   \&quot;polygon\&quot;: [       {\&quot;lon\&quot;:-74.0126609802,\&quot;lat\&quot;:40.6275684851 },       {\&quot;lon\&quot;:-74.0126609802,\&quot;lat\&quot;:40.7097269508 },       {\&quot;lon\&quot;:-73.9367866516,\&quot;lat\&quot;:40.7097269508 },       {\&quot;lon\&quot;:-73.9367866516,\&quot;lat\&quot;:40.6275684851 }   ],   \&quot;search_term\&quot; : \&quot;ENT\&quot; } &#x60;&#x60;&#x60; 
+    # ### Provider Details All searches can take a &#x60;search_term&#x60;, which is used as a component in the score (and thus the ranking/order) of the results.  This is combined with the proximity to the location in ranking results. For example, we would want \&quot;Dr. John Smith\&quot; who is 5 miles away from a given Zip Code to appear before \&quot;Dr. John Smith\&quot; who is 100 miles away.  The weighting also allows for non-exact matches.  In our prior example, we would want \&quot;Dr. Jon Smith\&quot; who is 2 miles away to appear before the exact match \&quot;Dr. John Smith\&quot; who is 100 miles away because it is more likely that the user just entered an incorrect name.  The free text search also supports Specialty name search and \&quot;body part\&quot; Specialty name search.  So, searching \&quot;John Smith nose\&quot; would return \&quot;Dr. John Smith\&quot;, the ENT Specialist before \&quot;Dr. John Smith\&quot; the Internist.  In addition, we can filter &#x60;Providers&#x60; by whether or not they accept *any* insurance.  Our data set includes over 4 million &#x60;Providers&#x60;, some of whom do not accept any insurance at all.  This filter makes it more likely that the user will find his or her practitioner in some cases.  ### Location Information  All &#x60;Provider&#x60; searches that do *not* specify &#x60;plan_ids&#x60; or &#x60;network_ids&#x60;require some type of location information. We use this information either to weight results or to filter results, depending on the type.  #### Zip Code When providing the &#x60;zip_code&#x60; parameter, we order the &#x60;Providers&#x60; returned based on their score, which incorporates their proximity to the given Zip Code and the closeness of match to the search text.  If a &#x60;radius&#x60; is also provided, we filter out &#x60;Providers&#x60; who are outside of that radius from the center of the Zip Code provided.  #### Polygon When providing the &#x60;polygon&#x60; parameter, we filter providers who are outside the bounds of the shape provided.  This is mutually exclusive with &#x60;zip_code&#x60; and &#x60;radius&#x60;.  ### Specialty When providing the &#x60;specialty_ids&#x60; parameter, we filter providers to those who practice those specialties. To find the specialty_ids, please use the [Specialty Search](#specialtes-specialtes-get) endpoint.  ### Plan/Network Information We can also filter based on &#x60;Plan&#x60; and &#x60;Network&#x60; participation, using &#x60;plan_ids&#x60; and &#x60;network_ids&#x60;, respectively.  These filters are mutually exclusive and return the union of the resulting sets for each &#x60;Plan&#x60; or &#x60;Network&#x60;.  I.e. if you provider Plan A and Plan B, you will receive &#x60;Providers&#x60; who accept *either* &#x60;Plan&#x60;.  The same is true for &#x60;Networks&#x60;. The plan identifiers filter supports: Vericred plan IDs returned from the [Dental](#header-dental-quotes) and [Vision](#header-vision-quotes) endpoints, as well as, HIOS IDs and Medicare contract codes.  ### Examples  *Find Dr. Foo near Brooklyn*  &#x60;{ \&quot;search_term\&quot;: \&quot;Foo\&quot;, \&quot;zip_code\&quot;: \&quot;11215\&quot; }&#x60;  *Find all Providers within 5 miles of Brooklyn who accept a Plan*  &#x60;{ \&quot;zip_code\&quot;: \&quot;11215\&quot;, \&quot;radius\&quot;: 5, \&quot;plan_ids\&quot;: [\&quot;88582NY0230001\&quot;] }&#x60;  *Find all providers on a map of Brooklyn ordered by a combination of proximity to the center point of the map and relevance to the search term \&quot;ENT\&quot;*  &#x60;&#x60;&#x60; {   \&quot;polygon\&quot;: [       {\&quot;lon\&quot;:-74.0126609802,\&quot;lat\&quot;:40.6275684851 },       {\&quot;lon\&quot;:-74.0126609802,\&quot;lat\&quot;:40.7097269508 },       {\&quot;lon\&quot;:-73.9367866516,\&quot;lat\&quot;:40.7097269508 },       {\&quot;lon\&quot;:-73.9367866516,\&quot;lat\&quot;:40.6275684851 }   ],   \&quot;search_term\&quot; : \&quot;ENT\&quot; } &#x60;&#x60;&#x60; 
     # @param body 
     # @param [Hash] opts the optional parameters
     # @return [Array<(ProvidersSearchResponse, Fixnum, Hash)>] ProvidersSearchResponse data, response status code and response headers

data/lib/vericred_client/api/quoting_api.rb

@@ -23,16 +23,18 @@ which we make available for several common programming languages.
 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"`
+`curl -H 'Vericred-Api-Key: YOUR_KEY' "https://api.vericred.com/drugs?search_term=Lipitor"`
 
 ## 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 `v4`.  We also support `v2` and `v3`
+The current version is `v6`.  We support prior versions. Our latest
+stable version is `v7` and we will indicate in the documentation for an
+endpoint if it's required.
 
-`curl -H 'Vericred-Api-Key: YOUR_KEY' -H 'Accept-Version: v3' "https://api.vericred.com/providers?search_term=Foo&zip_code=11215"`
+`curl -H 'Vericred-Api-Key: YOUR_KEY' -H 'Accept-Version: v6' "https://api.vericred.com/drugs?search_term=Lipitor"`
 
 ## Pagination
 
@@ -95,14 +97,14 @@ We also want the `name` and `code` from the `states` key, so we would
 add the parameters `select=states.name,states.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`
+Our final request would be `GET /providers/1234567898?select=provider.name,provider.phone,states.name,states.code`
 
 The response would be
 
 ```
 {
   provider: {
-    id: 1,
+    id: 1234567898,
     name: 'John',
     phone: '1234567890'
   },
@@ -333,6 +335,16 @@ The following are the supported Benefit Fields for Vision:
 - laser\_vision\_correction
 - additional\_pairs\_of\_eyeglasses
 
+### Medicare Advantage
+
+Medicare Advantage endpoints support MA (Medicare Advantage plans without prescription drug benefits), MAPD (Medicare Advantage plans with prescription drug benefits), and PDP (prescription drug benefits only) plans.
+
+Medical and hospital benefits - we support over 4000 individual plans through our API nationwide. At this time, we do not support EGHP (employer group health plans).
+
+Prescription drug benefits - drug benefits are categorized into initial coverage phase, coverage gap phase, and catastrophic phase. Each phase is broken down by drug tiers, pharmacy tiers, and length of supply.
+
+[Click here](#header-medicare-advantage-quotes) to learn more about quoting Medicare Advantage plans.
+
 ## Rates
 
 Rates are returned from the API as a part of [Quoting](#header-quoting).  We calculate Rates in one of two ways.
@@ -614,6 +626,19 @@ Note that in contrast to [Major Medical Quotes](#majormedicalquotes), [Vision Qu
 
 Also note that [Subsidies](#subsidies) and [Cost Sharing Reduction](#costsharingreductionplans) are *not* relevant for [Vision Quotes](#visionquotes).
 
+### Medicare Advantage quotes
+
+Given an enrollment date and location, you can search all plans available at this location using [/plans/medadv/search](#medicare-advantage-plans-medicare-advantage-plans-post); you can also search a specific plan using its plan ID with [/plans/medadv/{plan_id}](#medicare-advantage-plans-medicare-advantage-plans-get) if the plan ID is already known. The following example contains the required parameters:
+```
+{
+"zip_code": "02880",
+"fips_code": "44009",
+"enrollment_date": "2019-01-01"
+}
+```
+To view the technical documentation, [click here](#medicare-advantage-plans).
+
+
 ## Quotes for Groups
 A Group Quote finds [Plans](#header-plans) and [Rates](#header-rates) for a group of employees for a small business.  Different [Plans](#header-plans) are available to small groups than are available in [Individual Quoting](#individualquotes).  In addition, [Business Rules](#header-business-rules) that apply across multiple families or based upon employer attributes such as [SIC](https://en.wikipedia.org/wiki/Standard_Industrial_Classification) code factor into rates and availability.
 

data/lib/vericred_client/api/rates_api.rb

@@ -23,16 +23,18 @@ which we make available for several common programming languages.
 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"`
+`curl -H 'Vericred-Api-Key: YOUR_KEY' "https://api.vericred.com/drugs?search_term=Lipitor"`
 
 ## 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 `v4`.  We also support `v2` and `v3`
+The current version is `v6`.  We support prior versions. Our latest
+stable version is `v7` and we will indicate in the documentation for an
+endpoint if it's required.
 
-`curl -H 'Vericred-Api-Key: YOUR_KEY' -H 'Accept-Version: v3' "https://api.vericred.com/providers?search_term=Foo&zip_code=11215"`
+`curl -H 'Vericred-Api-Key: YOUR_KEY' -H 'Accept-Version: v6' "https://api.vericred.com/drugs?search_term=Lipitor"`
 
 ## Pagination
 
@@ -95,14 +97,14 @@ We also want the `name` and `code` from the `states` key, so we would
 add the parameters `select=states.name,states.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`
+Our final request would be `GET /providers/1234567898?select=provider.name,provider.phone,states.name,states.code`
 
 The response would be
 
 ```
 {
   provider: {
-    id: 1,
+    id: 1234567898,
     name: 'John',
     phone: '1234567890'
   },
@@ -333,6 +335,16 @@ The following are the supported Benefit Fields for Vision:
 - laser\_vision\_correction
 - additional\_pairs\_of\_eyeglasses
 
+### Medicare Advantage
+
+Medicare Advantage endpoints support MA (Medicare Advantage plans without prescription drug benefits), MAPD (Medicare Advantage plans with prescription drug benefits), and PDP (prescription drug benefits only) plans.
+
+Medical and hospital benefits - we support over 4000 individual plans through our API nationwide. At this time, we do not support EGHP (employer group health plans).
+
+Prescription drug benefits - drug benefits are categorized into initial coverage phase, coverage gap phase, and catastrophic phase. Each phase is broken down by drug tiers, pharmacy tiers, and length of supply.
+
+[Click here](#header-medicare-advantage-quotes) to learn more about quoting Medicare Advantage plans.
+
 ## Rates
 
 Rates are returned from the API as a part of [Quoting](#header-quoting).  We calculate Rates in one of two ways.
@@ -614,6 +626,19 @@ Note that in contrast to [Major Medical Quotes](#majormedicalquotes), [Vision Qu
 
 Also note that [Subsidies](#subsidies) and [Cost Sharing Reduction](#costsharingreductionplans) are *not* relevant for [Vision Quotes](#visionquotes).
 
+### Medicare Advantage quotes
+
+Given an enrollment date and location, you can search all plans available at this location using [/plans/medadv/search](#medicare-advantage-plans-medicare-advantage-plans-post); you can also search a specific plan using its plan ID with [/plans/medadv/{plan_id}](#medicare-advantage-plans-medicare-advantage-plans-get) if the plan ID is already known. The following example contains the required parameters:
+```
+{
+"zip_code": "02880",
+"fips_code": "44009",
+"enrollment_date": "2019-01-01"
+}
+```
+To view the technical documentation, [click here](#medicare-advantage-plans).
+
+
 ## Quotes for Groups
 A Group Quote finds [Plans](#header-plans) and [Rates](#header-rates) for a group of employees for a small business.  Different [Plans](#header-plans) are available to small groups than are available in [Individual Quoting](#individualquotes).  In addition, [Business Rules](#header-business-rules) that apply across multiple families or based upon employer attributes such as [SIC](https://en.wikipedia.org/wiki/Standard_Industrial_Classification) code factor into rates and availability.