Commerce & Payments · Integration
Thriva
Add Thriva to your product for your customers, and give your AI agents governed access to it.
Be plain about which Thriva this is. Alongside the consumer brand, Thriva runs a partner platform that other companies build on, and that is what an integration connects to: your customer holds their own Thriva partner credentials, and the people whose samples flow through are their end users, not yours. The objects are a test profile that says which biomarkers are measured, an order placed against a person, the fulfilment that ships a kit and gets a sample back to a lab, and the results and result sets that come out the other side. Two things deserve care. An order is physical, so a duplicate means a second kit posted and a second sample taken, which makes idempotent writes worth more here than in most integrations. And a biomarker result is personal health data, so the connection stays bound to a single tenant, exposes nothing beyond the fields you chose to map, and records each read.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer supply their own Thriva partner credentials so kits are ordered under their account and their end users stay theirs.
Place a test order from inside your product against the test profile the customer chose, idempotently, so a retry never posts a second kit.
Follow an order through fulfilment so your product can tell somebody where their kit is instead of asking them to wait.
Read biomarker results back into your own experience, mapping only the fields your product genuinely needs to show.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent checks where an order sits between dispatch and result without anyone opening a support ticket.
An agent places an approved order within scoped permissions, with the tenant and test profile it used recorded.
An agent summarises which orders are waiting on a sample return, reading only that partner's records.
Example prompt
Which test orders placed last month are still waiting on a sample, and how long has each been outstanding?
Set up Thriva in 4 steps
- 01Enable the Thriva connector in your fastn dashboard.
- 02Have each customer supply credentials for their own Thriva partner account, since this is a partner platform rather than a consumer login.
- 03Map the test profile, order and result fields your product uses, and decide which biomarker data you are willing to hold.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Thriva integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Thriva integration without building it. Your customers connect their own Thriva account inside your product and work their orders, payments and customers there, with no per-customer code on your side.
- Handle the part that actually costs time: money and order state must never be double-applied, and reconciliation has to be possible. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Thriva update is not your on-call problem.
- One integration serves your product and your agents. The same governed Thriva connection powers in-product features and gives AI agents scoped, audited access, so you keep commerce and payment records in step with your product without wiring it twice.
Used by these teams
Works well with
Metriport
Redox EngineOften used alongside
Tools the same teams tend to run next to Thriva, across other categories.
NetSuite
Notion
Box
DocusignThriva integration FAQ
How do I add a Thriva integration to my product?
Enable the Thriva connector in your fastn dashboard, then let each customer authenticate their own Thriva account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Thriva client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Thriva account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Thriva account and only ever sees their own orders, payments and customers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Thriva integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent checks where an order sits between dispatch and result without anyone opening a support ticket.
Who maintains the Thriva integration?
fastn does. When Thriva changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the Thriva integration safe for payment and order writes?
Writes are idempotent, so a retry cannot double-charge or duplicate an order, and every call is logged per tenant so a transaction can be reconciled against the event that triggered it.
Can my product react to a new order, payment or refund immediately?
Yes, through event triggers, so fulfilment, entitlement or accounting steps run as soon as the event lands rather than on a nightly sync.
What can I build with the Thriva integration?
A common starting point: let each customer supply their own Thriva partner credentials so kits are ordered under their account and their end users stay theirs. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Thriva integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Thriva does not change your per-connector cost. You can start free with 3 connected accounts.
Add Thriva to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.