pVerify API Walkthrough

Creating a general application where you need access to key information such as plan info, status, deductible, and out of pocket? pVerify has you covered!

 

In three simple steps, you can have your first call returned with key information relating to each of the above areas.

Step 1: Obtain your ID and secret from API Management site Overview Page

Step 2: Perform a token call:

					

https://api.pverify.com/Token POST 
Body: Client_Id=(your id)&client_secret=(your secret)&grant_type=client_credentials

Response:

{ "access_token": "4QZq1-EbfK0E...", "token_type": "bearer", "expires_in": 3599, "ClientUserID": "46", "ClientID": "12" }

Step 3: Perform downstream call – example Elig Summary

– Note EITHER subscriber OR dependent FIRST/LAST/DOB must be present.
– Note In all downstream calls the Client-API-Id header must be included with your API ID (from Token call).
Optionally you can use Client-User-Name
– Note either use pVerify payer codes (00001 for Aetna) or use your own codes and perform mapping in our system (contact us for information).
– Note for Medicare – CMS must register the NPI – this is a manual process and takes 2-3 days.
 
					

https://api.pverify.com/API/EligibilitySummary POST

Authorization: Bearer (the token response from step 2)
Client-API-Id: (your API ID from Token call)
Content-Type: application/json
Body:
{ "payerCode": "Aetna", "provider": { "firstName": "<>", "middleName": "", "lastName": "<>" }, "subscriber": { "firstName": " <> ", "middleName": "", "lastName": " << YOUR SUBSCRIBER LAST NAME>> ", "dob": " <> ", "memberId": "<< YOUR MEMBER ID>>" }, "dependent": { "patient": { "firstName": "<>", "middleName": "", "lastName": "<< YOUR DEPENDANT LAST NAME>>", "dob": "<>", "gender": "" }, "relationWithSubscriber": "" }, "isSubscriberPatient": "<>", "doS_StartDate": "11/01/2019", "doS_EndDate": "11/01/2019", "requestSource": "RestAPI", "referenceId": "123", "Location": "TX", "IncludeTextResponse": false }

Need more information?

Here you can create the content that will be used within the module.