Integration paths

Pick the path that matches who owns the source system and what should happen to the files after they reach Relu.

All tooth numbers use FDI notation

Whatever path you pick: the API accepts FDI (ISO 3950) tooth numbers only — convert Universal (UNN) numbers before calling. See Tooth numbering.

For a private lab sending cases from its own LMS or scan intakeInbox intake

Upload the case files for review and later automation. Your server calls the Inbox API with an API key. This does not create an order.

For internal labs or third parties connecting to ReluAPI integration

You want to programmatically create orders and pull results. REST API only. Works for your own lab's automation or for a partner product calling our API.

For an LMS or scan-intake product used by several labsManaged Inbox source

Expose a tenant-aware case and file API. Relu owns the connector and maps each authenticated provider tenant to the correct lab.

For products exposing Relu services to end usersIframe + draft orders

Your users interact with Relu through your product. Use the iframe viewer and the draft-order flow with assumed user tokens.

For workflows that push & pull data without writing codeRelu Agents

You don't want to hit the API directly. Let Relu Agents move data in and out of your systems.

For integrators already on our previous platformMigrate from Relu Engine

You already use Relu Engine. Map your existing calls onto Automate's service-based API.

Not sure which fits?

Most integrators fall into one of these buckets:

Your lab wants existing cases and scans to appear in the Inbox → Inbox intake.
Your LMS or scan-intake product serves several labs → Managed Inbox source.
Your lab knows which Relu service to run and wants an order immediately → API integration.
Your product ships Relu services to thousands of dentists → Iframe + draft orders.
You have an existing data pipeline and want Relu bolted on → Relu Agents.
You're already on Relu Engine and want the newer platform → Migration.

For a managed Inbox source, contact Relu support before building. Do not ask every lab to place a Relu API key in the shared product.

Not sure which fits?

On this page