Skip to main content

​
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
  • 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
Last updated: 2025-09-11 21:55 UTC