Payer follow-ups
Payments
Read one payer's public application status page now: send the page, the clinician's NPI, the state, and the numbers that page asks for (the application number, the clinician's last name as submitted, the practice's EIN), with the submitted date if known. Returns what the page said (its status words, the date it gives, the application number it shows, an excerpt), the page's address and the time it was read. A page that needs a person (one read by hand, a sign-in, nothing or several found, a decision to confirm, a number not given) says so with the reason; nothing is guessed and nothing is recorded on any application. Needs a credentialing firm's access token, or a paid follow-up's own access token (not an emailed link's). Up to 12 checks per 10 minutes and 60 per day per caller, and up to 30 reads of one payer's page per 10 minutes in all.
The access token goes in the X-Payer-Follow-Up-Token header, Authorization: Bearer, or the token field. outcome read: the page stated a status (status is received, in_review or no_record). outcome needs_person: blocker says why (captcha, bot_challenge, login_wall, shape_changed, missing_numbers, not_found, several_found, needs_detail, decision, unknown_status, unreachable) and reason says it in words; page_status still carries what the page showed, if anything. Only the NPI and what the page said are kept; the other numbers typed are not.
post/v1/payer-follow-ups/status-check
Request
- Base URL: https://www.licium.ai
- URL: https://www.licium.ai/v1/payer-follow-ups/status-check
- Auth: none required
Headers
X-Payer-Follow-Up-Tokenstring
A credentialing firm's access token, or a paid follow-up's own access token.
Request body
Response
What the page said.
Changes
No recorded changes to this operation across all 1 revision of this API.