Skip to content

Blog

Upcoming change for all partners using iTero Generic API

A mandatory change that will happen in the near future is the move from OAuth2.0 to Auth0.

All Partners will have to move to Auth0 to continue using the iTero Generic API.

iTero will make an initial announcement with the details of the change and what's necessary to update. During the transition period, both OAuth2.0 and Auth0 will be supported concurrently. This dual support is designed to give partners ample time to make the switch without disrupting their operations.

Deadlines for the move will be shared when the information becomes available. It is important to stay vigilant to the iTero newsletter and plan your transition accordingly to avoid any service interruptions

Any questions or concerns can be addressed to the official support email: iteroapisupport@gmail.com

Note

New partners that wish to create a connection with iTero should keep in mind that an additional overhead will be required for the integration to move from OAuth2.0 to Auth0 in the future.


New Feature - Delete Rx

Image


RX is the first step for a successful scan. You can create an RX directly from the scanner or from a DPMS with an iTero connection.

It is a good practice to store each RXID returned by the Scan Request endpoint. This allows you to match incoming scans to their corresponding RX.



What if an RX is created but never used?

With the new Delete RX endpoint, you can now delete RXs directly from the DPMS, ensuring consistency between the DPMS and the scanner. An RX can also be deleted from the scanner that created it.

To delete an RX, use the following DELETE operation on the scan-request endpoint:

DELETE /api/third-party/v2/scan-request/:RXID

Simply pass the RXID, and the endpoint will remove the RX.

Note

RXs can be deleted. However, scans can't be deleted.

If you’d like to try this feature and don’t have access to a scanner, you can use the iTero portal at myitero.com to view and test RX deletions. Any deleted RX will be removed from the orders dashboard.

New Feature: Discovery API - Regional URL's for API calls

We're pleased to announce that V2 of iTero's Generic API can now implement Discovery API.

Discovery API prevents regional problems like ISP routing from affecting the end user experience and integration functionality. This helps prevent issues like false 'not paired' messages, orders not found, and more.
The regional value returned is retrieved from the clinic's or lab's address in the internal iTero system.

Image