pVerify · Authentication Profile
Pverify Authentication
Authentication
pVerify uses a two-factor-by-header model: an OAuth2 client-credentials bearer token obtained from POST /Token, sent alongside a Client-API-Id header that identifies the account. Both are required on every call. A small set of "one step" endpoints skips the token entirely and authenticates with Client-API-Id + Client-Secret headers, and one endpoint (GetPayerStatus) is documented as requiring no authentication at all.
pVerify secures its APIs with http and apiKey across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).
HealthcareInsuranceEligibilityClaimsEDI270/271276/277Revenue CycleMedicarePayersInsurance DiscoveryPatient EstimationHIPAADental
Methods: http, apiKey
Schemes: 3
OAuth flows: clientCredentials
API key in: header
Security Schemes
bearerAuth http
clientApiId apiKey
clientSecret apiKey
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.