Note the June 2026 rebrand: CAQH is now DataSpring, powered by CAQH (rebranded June 8, 2026); the Provider Data Portal, credentials, and API surface remain operationally unchanged — update internal documentation and vendor references to use the new brand name.
Obtain API credentials from DataSpring by completing the organization registration process; the API is typically available to health plans and credentialing organizations, not individual providers — confirm your access tier.
Use the DataSpring Provider Data Portal API to retrieve provider records by NPI; inspect the attestation date field to identify providers whose 120-day re-attestation window is approaching or has lapsed.
For providers with expiring attestation, send an automated outreach notification with a direct link to the DataSpring portal re-attestation flow; do not attempt to programmatically attest on behalf of a provider — attestation requires the provider's own login and consent.
After the provider completes re-attestation, pull the updated record via the API and push the refreshed data to your credentialing system of record and provider directory; verify the updated attestation timestamp.
Build a reconciliation report that flags providers whose DataSpring attestation has lapsed beyond your credentialing policy tolerance and routes them to the credentialing team for follow-up or temporary network suspension review.
Known gotchas
DataSpring enforces a 120-day attestation cycle; a provider record that has not been re-attested within that window is flagged as unverified by DataSpring regardless of what your internal system shows — do not rely solely on your own credentialing database.
The DataSpring API access model is organization-based; health plans access provider data only for providers who have authorized the plan — providers who revoke authorization disappear from your API results without an explicit notification.
The rebrand from CAQH to DataSpring is recent (June 2026); some payers, EMR systems, and partner integrations may still use 'CAQH' in their UI or API parameters — verify that existing integrations still resolve correctly to the new domain.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp