Vericred's API allows you to search for Health Plans that a specific doctor accepts.
Visit our Developer Portal 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).
Our API follows standard REST conventions, so you can use any HTTP client to integrate with us. You will likely find it easier to use one of our autogenerated SDKs, 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"
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"
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.
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
.
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.
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'
}]
}
Benefit cost-share strings are formatted to capture:
- Network tiers
- Compound or conditional cost-share
- Limits on the cost-share
- Benefit-specific maximum out-of-pocket costs
Example #1 As an example, we would represent this Summary of Benefits & Coverage as:
-
Hospital stay facility fees:
- Network Provider:
$400 copay/admit plus 20% coinsurance
- Out-of-Network Provider:
$1,500 copay/admit plus 50% coinsurance
- Vericred's format for this benefit:
In-Network: $400 before deductible then 20% after deductible / Out-of-Network: $1,500 before deductible then 50% after deductible
- Network Provider:
-
Rehabilitation services:
- Network Provider:
20% coinsurance
- Out-of-Network Provider:
50% coinsurance
- Limitations & Exceptions:
35 visit maximum per benefit period combined with Chiropractic care.
- Vericred's format for this benefit:
In-Network: 20% after deductible / Out-of-Network: 50% after deductible | limit: 35 visit(s) per Benefit Period
- Network Provider:
Example #2 In this other Summary of Benefits & Coverage, the specialty_drugs cost-share has a maximum out-of-pocket for in-network pharmacies.
- Specialty drugs:
- Network Provider:
40% coinsurance up to a $500 maximum for up to a 30 day supply
- Out-of-Network Provider
Not covered
- Vericred's format for this benefit:
In-Network: 40% after deductible, up to $500 per script / Out-of-Network: 100%
- Network Provider:
BNF
Here's a description of the benefits summary string, represented as a context-free grammar:
<cost-share> ::= <tier> <opt-num-prefix> <value> <opt-per-unit> <deductible> <tier-limit> "/" <tier> <opt-num-prefix> <value> <opt-per-unit> <deductible> "|" <benefit-limit>
<tier> ::= "In-Network:" | "In-Network-Tier-2:" | "Out-of-Network:"
<opt-num-prefix> ::= "first" <num> <unit> | ""
<unit> ::= "day(s)" | "visit(s)" | "exam(s)" | "item(s)"
<value> ::= <ddct_moop> | <copay> | <coinsurance> | <compound> | "unknown" | "Not Applicable"
<compound> ::= <copay> <deductible> "then" <coinsurance> <deductible> | <copay> <deductible> "then" <copay> <deductible> | <coinsurance> <deductible> "then" <coinsurance> <deductible>
<copay> ::= "$" <num>
<coinsurace> ::= <num> "%"
<ddct_moop> ::= <copay> | "Included in Medical" | "Unlimited"
<opt-per-unit> ::= "per day" | "per visit" | "per stay" | ""
<deductible> ::= "before deductible" | "after deductible" | ""
<tier-limit> ::= ", " <limit> | ""
<benefit-limit> ::= <limit> | ""
This C# SDK is automatically generated by the Swagger Codegen project:
- API version: 1.0.0
- SDK version: 0.0.6
- Build package: class io.swagger.codegen.languages.CSharpClientCodegen
- .NET 4.0 or later
- Windows Phone 7.1 (Mango)
The DLLs included in the package may not be the latest version. We recommned using [NuGet] (https://docs.nuget.org/consume/installing-nuget) to obtain the latest version of the packages:
Install-Package RestSharp
Install-Package Newtonsoft.Json
NOTE: RestSharp versions greater than 105.1.0 have a bug which causes file uploads to fail. See RestSharp#742
Run the following command to generate the DLL
- [Mac/Linux]
/bin/sh build.sh
- [Windows]
build.bat
Then include the DLL (under the bin
folder) in the C# project, and use the namespaces:
using IO.Vericred.Api;
using IO.Vericred.Client;
using Model;
using System;
using System.Diagnostics;
using IO.Vericred.Api;
using IO.Vericred.Client;
using Model;
namespace Example
{
public class Example
{
public void main()
{
// Configure API key authorization: Vericred-Api-Key
Configuration.Default.ApiKey.Add("Vericred-Api-Key", "YOUR_API_KEY");
// Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
// Configuration.Default.ApiKeyPrefix.Add("Vericred-Api-Key", "Bearer");
var apiInstance = new DrugPackagesApi();
var formularyId = 123; // string | ID of the Formulary in question
var ndcPackageCode = 07777-3105-01; // string | ID of the DrugPackage in question
try
{
// Formulary Drug Package Search
FormularyDrugPackageResponse result = apiInstance.ShowFormularyDrugPackageCoverage(formularyId, ndcPackageCode);
Debug.WriteLine(result);
}
catch (Exception e)
{
Debug.Print("Exception when calling DrugPackagesApi.ShowFormularyDrugPackageCoverage: " + e.Message );
}
}
}
}
All URIs are relative to https://api.vericred.com/
Class | Method | HTTP request | Description |
---|---|---|---|
DrugPackagesApi | ShowFormularyDrugPackageCoverage | GET /formularies/{formulary_id}/drug_packages/{ndc_package_code} | Formulary Drug Package Search |
DrugsApi | GetDrugCoverages | GET /drug_packages/{ndc_package_code}/coverages | Search for DrugCoverages |
DrugsApi | ListDrugs | GET /drugs | Drug Search |
NetworkSizesApi | ListStateNetworkSizes | GET /states/{state_id}/network_sizes | State Network Sizes |
NetworkSizesApi | SearchNetworkSizes | POST /network_sizes/search | Network Sizes |
NetworksApi | ListNetworks | GET /networks | Networks |
NetworksApi | ShowNetwork | GET /networks/{id} | Network Details |
PlansApi | FindPlans | POST /plans/search | Find Plans |
PlansApi | ShowPlan | GET /plans/{id} | Show Plan |
ProvidersApi | GetProvider | GET /providers/{npi} | Find a Provider |
ProvidersApi | GetProviders | POST /providers/search | Find Providers |
ProvidersApi | GetProviders_0 | POST /providers/search/geocode | Find Providers |
ZipCountiesApi | GetZipCounties | GET /zip_counties | Search for Zip Counties |
- Model.Applicant
- Model.Carrier
- Model.CarrierSubsidiary
- Model.County
- Model.CountyBulk
- Model.Drug
- Model.DrugCoverage
- Model.DrugCoverageResponse
- Model.DrugPackage
- Model.DrugSearchResponse
- Model.Formulary
- Model.FormularyDrugPackageResponse
- Model.FormularyResponse
- Model.Meta
- Model.ModelBase
- Model.Network
- Model.NetworkDetails
- Model.NetworkDetailsResponse
- Model.NetworkSearchResponse
- Model.NetworkSize
- Model.Plan
- Model.PlanCounty
- Model.PlanCountyBulk
- Model.PlanSearchResponse
- Model.PlanSearchResponseMeta
- Model.PlanSearchResult
- Model.PlanShowResponse
- Model.Pricing
- Model.Provider
- Model.ProviderDetails
- Model.ProviderGeocode
- Model.ProviderShowResponse
- Model.ProvidersGeocodeResponse
- Model.ProvidersSearchResponse
- Model.RatingArea
- Model.RequestPlanFind
- Model.RequestPlanFindApplicant
- Model.RequestPlanFindDrugPackage
- Model.RequestPlanFindProvider
- Model.RequestProvidersSearch
- Model.ServiceArea
- Model.ServiceAreaZipCounty
- Model.State
- Model.StateNetworkSizeRequest
- Model.StateNetworkSizeResponse
- Model.VendoredPlanBulk
- Model.ZipCode
- Model.ZipCountiesResponse
- Model.ZipCounty
- Model.ZipCountyBulk
- Model.ZipCountyResponse
- Type: API key
- API key parameter name: Vericred-Api-Key
- Location: HTTP header