# Adjudication decision created Source: https://docs.thrivory.com/api-reference/adjudication-decision-created api-reference/openapi.json webhook adjudication.decision # Cancel an adjudication/settlement prior to funding Source: https://docs.thrivory.com/api-reference/adjudications-&-settlements/cancel-an-adjudicationsettlement-prior-to-funding api-reference/openapi.json post /v1/settlements/{settlement_id}/cancel # Confirm terms and release funds Source: https://docs.thrivory.com/api-reference/adjudications-&-settlements/confirm-terms-and-release-funds api-reference/openapi.json post /v1/settlements/{settlement_id}/confirm # Create adjudication + terms using authorization_id Source: https://docs.thrivory.com/api-reference/adjudications-&-settlements/create-adjudication-+-terms-using-authorization_id api-reference/openapi.json post /v1/claims/adjudications # Reconciliation details for a funded settlement Source: https://docs.thrivory.com/api-reference/adjudications-&-settlements/reconciliation-details-for-a-funded-settlement api-reference/openapi.json get /v1/settlements/{settlement_id}/reconciliation # Introspect a token (optional) Source: https://docs.thrivory.com/api-reference/auth/introspect-a-token-optional api-reference/openapi.json post /v1/oauth/introspect # JWKS for signature verification Source: https://docs.thrivory.com/api-reference/auth/jwks-for-signature-verification api-reference/openapi.json get /.well-known/jwks.json # Obtain an access token (OAuth 2.0 Client Credentials) Source: https://docs.thrivory.com/api-reference/auth/obtain-an-access-token-oauth-20-client-credentials api-reference/openapi.json post /v1/oauth/token # Revoke a token (optional) Source: https://docs.thrivory.com/api-reference/auth/revoke-a-token-optional api-reference/openapi.json post /v1/oauth/revoke # Authoritative claim status update Source: https://docs.thrivory.com/api-reference/authoritative-claim-status-update api-reference/openapi.json webhook claim.status.updated # Claim review result Source: https://docs.thrivory.com/api-reference/claim-review-result api-reference/openapi.json webhook claim.reviewed # Fetch a claim rollup (review + adjudication + status) Source: https://docs.thrivory.com/api-reference/claims/fetch-a-claim-rollup-review-+-adjudication-+-status api-reference/openapi.json get /v1/claims/{claim_id} # Fetch Thrivory's current claim status Source: https://docs.thrivory.com/api-reference/claims/fetch-thrivorys-current-claim-status api-reference/openapi.json get /v1/claims/{claim_id}/status # Review a claim (predictions, no funding) Source: https://docs.thrivory.com/api-reference/claims/review-a-claim-predictions-no-funding api-reference/openapi.json post /v1/claims/reviews # Signal a claim status update Source: https://docs.thrivory.com/api-reference/claims/signal-a-claim-status-update api-reference/openapi.json patch /v1/claims/{claim_id}/status # Bulk import historical claims (async job) Source: https://docs.thrivory.com/api-reference/imports/bulk-import-historical-claims-async-job api-reference/openapi.json post /v1/imports/claims # Fetch import job status Source: https://docs.thrivory.com/api-reference/imports/fetch-import-job-status api-reference/openapi.json get /v1/imports/{job_id} # Available funding rails and cutoff times Source: https://docs.thrivory.com/api-reference/metadata/available-funding-rails-and-cutoff-times api-reference/openapi.json get /v1/metadata/funding-rails # Search payers (Thrivory Payer IDs) Source: https://docs.thrivory.com/api-reference/metadata/search-payers-thrivory-payer-ids api-reference/openapi.json get /v1/metadata/payers Returns payer directory entries. Use `system=internal` to filter to Thrivory payer identifiers. # Thrivory proprietary denial reason codes Source: https://docs.thrivory.com/api-reference/metadata/thrivory-proprietary-denial-reason-codes api-reference/openapi.json get /v1/metadata/reason-codes # Health check Source: https://docs.thrivory.com/api-reference/operations/health-check api-reference/openapi.json get /v1/health # Delete payout account Source: https://docs.thrivory.com/api-reference/payout-accounts/delete-payout-account api-reference/openapi.json delete /v1/payout-accounts/{id} # Get payout account Source: https://docs.thrivory.com/api-reference/payout-accounts/get-payout-account api-reference/openapi.json get /v1/payout-accounts/{id} # List payout accounts Source: https://docs.thrivory.com/api-reference/payout-accounts/list-payout-accounts api-reference/openapi.json get /v1/payout-accounts # Register a tokenized payout destination Source: https://docs.thrivory.com/api-reference/payout-accounts/register-a-tokenized-payout-destination api-reference/openapi.json post /v1/payout-accounts # Reconciliation event posted Source: https://docs.thrivory.com/api-reference/reconciliation-event-posted api-reference/openapi.json webhook reconciliation.posted # Settlement failed Source: https://docs.thrivory.com/api-reference/settlement-failed api-reference/openapi.json webhook settlement.failed # Settlement funded Source: https://docs.thrivory.com/api-reference/settlement-funded api-reference/openapi.json webhook settlement.funded # Create webhook endpoint Source: https://docs.thrivory.com/api-reference/webhooks/create-webhook-endpoint api-reference/openapi.json post /v1/webhooks/endpoints # Delete webhook endpoint Source: https://docs.thrivory.com/api-reference/webhooks/delete-webhook-endpoint api-reference/openapi.json delete /v1/webhooks/endpoints/{id} # Get webhook endpoint Source: https://docs.thrivory.com/api-reference/webhooks/get-webhook-endpoint api-reference/openapi.json get /v1/webhooks/endpoints/{id} # List webhook endpoints Source: https://docs.thrivory.com/api-reference/webhooks/list-webhook-endpoints api-reference/openapi.json get /v1/webhooks/endpoints # Rotate webhook signing secret Source: https://docs.thrivory.com/api-reference/webhooks/rotate-webhook-signing-secret api-reference/openapi.json post /v1/webhooks/endpoints/{id}/rotate-secret # Send a test event to a webhook endpoint Source: https://docs.thrivory.com/api-reference/webhooks/send-a-test-event-to-a-webhook-endpoint api-reference/openapi.json post /v1/webhooks/test # Thrivory Source: https://docs.thrivory.com/index Embed instant adjudication, reimbursement predictions, and funding into your platform via a unified, HIPAA‑aligned API. # ThriveNow API ThriveNow brings **embedded finance** directly into your practice management or RCM platform. With one integration you can **predict denial risk**, **estimate reimbursement**, **forecast payment timelines**, **adjudicate and fund** eligible claims, and **reconcile** payouts—without disrupting existing workflows. *** ## About Thrivory Thrivory provides **non‑recourse, claim‑to‑payment** financing and AI‑powered claim intelligence so providers can turn receivables into working capital. We assume reimbursement risk on approved advances while keeping billing and clearinghouse flows unchanged. * **No loans or personal guarantees** — asset sale model * **Fast access to capital** — advances on approved claims * **Keep your stack** — we integrate alongside your PMS/RCM *** ## What ThriveNow does * **Predict Claim Denial Risk** — real‑time probability + proprietary reason codes * **Predict Expected Reimbursement** — allowed and expected amounts * **Predict Reimbursement Timeline** — expected payment date with confidence * **Adjudicate & Fund** — create terms and release funds (`RTP`, `SAME_DAY`, `FUTURE_DATE`) * **Automated Reconciliation** — match payer deposits to prior advances and settle fees * **Unified API** — consistent REST under `/v1`, OAuth 2.0, idempotency, and webhooks *** ## Security & compliance * **HIPAA** with BAA (required for production) * **Encryption:** TLS 1.2+ in transit, AES‑256 at rest * **Access controls:** OAuth 2.0 (client credentials), RBAC, audit logs * **Webhooks:** HMAC header **`Thrivory-Signature`**; verify before processing * **Hosting & monitoring:** hardened infrastructure with continuous monitoring > Thrivory follows a **minimum‑necessary PHI** approach. Only send what’s required for prediction and settlement. *** ## Start here * **Quickstart:** end‑to‑end setup and sample calls → [Quickstart](/quickstart) * **API Reference:** autogenerated from our OpenAPI 3.1 spec (see the **API reference** tab) * **Production access:** requires a **BAA** and standard security diligence *** ## Endpoints (at a glance) All endpoints are prefixed with **`/v1`**: * **Auth:** `POST /v1/oauth/token` * **Claim Review:** `POST /v1/claims/reviews` → returns `authorization_id` * **Adjudication:** `POST /v1/claims/adjudications`, `POST /v1/settlements/{settlement_id}/confirm` * **Status:** `PATCH /v1/claims/{claim_id}/status`, `GET /v1/claims/{claim_id}/status`, `GET /v1/claims/{claim_id}` * **Reconciliation:** `GET /v1/settlements/{settlement_id}/reconciliation` * **Metadata:** `GET /v1/metadata/payers` (use **Available Payer IDs**), `GET /v1/metadata/reason-codes`, `GET /v1/metadata/funding-rails` See the **API reference** for full schemas, examples, and webhooks. *** ## Errors We use standard HTTP status codes: * `200` Success * `400` Validation error * `401` Unauthorized * `404` Not found * `500` Server error Error payloads include `error`, `message`, optional `request_id`, and `details`. *** ## Support Need sandbox credentials, a BAA template, or security docs?\ **Email:** [support@thrivory.com](mailto:support@thrivory.com) *** *Last updated: 2025-09-11 21:55 UTC* # Quickstart Source: https://docs.thrivory.com/quickstart Integrate ThriveNow — authenticate, review a claim, create terms, confirm funding, and receive webhooks. # Quickstart This guide gets you from zero to a working integration with the **ThriveNow API**: obtain an access token, **review** a claim to get predictions and an `authorization_id`, **adjudicate** to create terms, **confirm** funding, and receive **webhooks** for status and reconciliation. > **Prerequisites** > > * A **Business Associate Agreement (BAA)** with Thrivory for production use. > * **Sandbox credentials** (OAuth 2.0 Client Credentials). > * A publicly reachable **HTTPS** endpoint for webhooks. > * Minimal‑PHI integration: send only fields required for prediction/settlement. *** ## 1) Configure your environment ```bash theme={null} export THRIVORY_BASE_URL="https://api.sandbox.thrivory.com" # or production URL after approval export THRIVORY_CLIENT_ID="" export THRIVORY_CLIENT_SECRET="" export THRIVORY_TOKEN_FILE="./thrivory_token.json" ``` *** ## 2) Get an access token (OAuth 2.0 Client Credentials) ```bash theme={null} curl -s -X POST "$THRIVORY_BASE_URL/v1/oauth/token" -H "Content-Type: application/json" -d '{ "client_id": "'"$THRIVORY_CLIENT_ID"'", "client_secret": "'"$THRIVORY_CLIENT_SECRET"'", "grant_type": "client_credentials" }' | tee "$THRIVORY_TOKEN_FILE" ``` ```bash theme={null} export THRIVORY_ACCESS_TOKEN="$(jq -r .access_token < "$THRIVORY_TOKEN_FILE")" ``` *** ## 3) (Optional) Look up a payer (Thrivory IDs available upon request) ```bash theme={null} curl -s "$THRIVORY_BASE_URL/v1/metadata/payers?q=Aetna&system=internal" -H "Authorization: Bearer $THRIVORY_ACCESS_TOKEN" ``` Use the returned **Thrivory Payer ID** as `patient_primary_payor_id`. *** ## 4) Review a claim (predictions + authorization\_id) ```bash theme={null} curl -s -X POST "$THRIVORY_BASE_URL/v1/claims/reviews" -H "Authorization: Bearer $THRIVORY_ACCESS_TOKEN" -H "Content-Type: application/json" -H "Idempotency-Key: demo-claim-001" -d '{ "facility": "ABC", "claim_identifier": "CLM-10001", "chart_identifier": "PAT-5678", "date_of_service": "2025-08-15", "date_of_submission": "2025-08-16", "servicer_npi": "1111111111", "billing_npi": "5556667778", "patient_primary_payor_id": "thrivoryid:123456", "submitted_amount": 5000, "service_lines": [ { "cpt": "J1745", "modifier": "JW", "units": 1, "amount": 5000 } ] }' ``` **Example response** ```json theme={null} { "id": "rvw_123", "authorization_id": "auth_abc123", "denial_predicted": false, "denial_reasons": [], "expected_reimbursement": { "allowed": 4800, "expected": 4800 }, "expected_payment_date": "2025-09-29", "confidence": 0.91 } ``` > Use `authorization_id` in the next step to create adjudication terms. *** ## 5) Create adjudication terms (funding options) ```bash theme={null} curl -s -X POST "$THRIVORY_BASE_URL/v1/claims/adjudications" -H "Authorization: Bearer $THRIVORY_ACCESS_TOKEN" -H "Content-Type: application/json" -H "Idempotency-Key: demo-adj-001" -d '{ "authorization_id": "auth_abc123", "funding": { "rail": "SAME_DAY" }, "payout_account_token": "bank_tok_abc123" }' ``` **Example response** ```json theme={null} { "settlement_id": "stl_987654321", "decision": "approved", "terms": { "advance_percentage": 0.80, "advance_amount": 3840, "fees_estimate": 96 }, "status": "pending_confirmation", "expected_reimbursement": 4800, "expected_payment_date": "2025-09-29" } ``` *** ## 6) Confirm funding ```bash theme={null} curl -s -X POST "$THRIVORY_BASE_URL/v1/settlements/stl_987654321/confirm" -H "Authorization: Bearer $THRIVORY_ACCESS_TOKEN" -H "Idempotency-Key: demo-confirm-001" ``` **Example response** ```json theme={null} { "settlement_id": "stl_987654321", "status": "funded", "funded_amount": 3840, "timestamp": "2025-09-09T14:32:00Z" } ``` *** ## 7) Subscribe to webhooks Configure your endpoint to verify the **Thrivory-Signature** (HMAC SHA-256) header. Webhook payloads use a common envelope. **Example — `reconciliation.posted`** ```json theme={null} { "event": "reconciliation.posted", "id": "evt_12345", "created_at": "2025-09-30T12:01:22Z", "data": { "id": "rcn_001", "settlement_id": "stl_987654321", "payer_payment": 4800, "fee_collected": 96, "final_status": "closed" } } ``` *** ## Go-live checklist * BAA executed + security review complete * Least‑privilege OAuth client + key rotation policy * Webhook signature verification with retries/backoff * Logging/audit for PHI access and operational events * Idempotent POSTs with `Idempotency-Key` *** ## Troubleshooting * **400 – Validation error**: Check required fields (`claim_identifier`, `chart_identifier`, `servicer_npi`, `billing_npi`, `patient_primary_payor_id`, `submitted_amount`). * **401 – Unauthorized**: Token expired/invalid. Refresh credentials. * **404 – Not found**: Invalid `settlement_id` or `claim_id`. * **500 – Server error**: Transient. Retry with backoff (idempotent). *** ## Support Need sandbox credentials or a BAA template?\ **Email:** [support@thrivory.com](mailto:support@thrivory.com) *** *Last updated: 2025-09-11 21:22 UTC*