We have a question about how to handle a prerequisite on the partner side during account linking.
In our architecture, Ring linking can only complete if the customer already has:
The reason is that our registered IoT system is the component that stores the Ring access and refresh tokens and makes the Partner API calls. Because of that, we do not currently support a flow where a user starts from Ring linking first, and only afterward creates a partner account and registers the IoT system.
In other words, if the customer does not already have our account and registered system in place, the Ring callback cannot fully complete on our side.
What is the recommended way to present this to users?
Is it acceptable to make this prerequisite explicit in the linking UX and say something like:
“A SAVI IQ account and a registered SAVI IQ system are required before Ring can be connected.”
And for certification/review, is this the kind of prerequisite that should simply be documented clearly in the reviewer notes and in the linking flow, or does Ring expect a different pattern?
We want to make sure we are communicating this dependency in the recommended way.
Hi Darrell,
Your approach is valid and aligns with how the account linking flow is designed.
Is it acceptable to require a partner account and registered system before Ring linking?
Yes. The Account Link URL is your page, you control what happens there. Ring mandates that users sign in to your partner service at this step, but any additional prerequisites you require (like having a registered IoT system) are your design decision. If a user arrives at your Account Link URL without meeting your prerequisites, you can display a clear message explaining what’s needed and how to proceed.
Something like this is perfectly fine:
“A SAVI IQ account and a registered SAVI IQ system are required before Ring can be connected. Please set up your system first, then return to the Ring AppStore to connect.”
The UX design guidelines emphasize that error states should explain what went wrong in plain language and offer a clear next step, so as long as your messaging is helpful and not a dead end, this is the right pattern.
For certification:
Document this prerequisite clearly in your reviewer notes. The certification form asks “How can a Ring reviewer create an account on your platform?” and “How can a Ring reviewer test the end-to-end integration?”, use those fields to explain:
-
How the reviewer can create a SAVI IQ account
-
How to register a test system (or provide a pre-configured test account that already has one)
-
Then walk them through the Ring linking flow
As long as the reviewer can complete the full flow with the instructions you provide, this should pass certification without issue. The key is that QA can test it end-to-end, the prerequisite itself is not a problem, but the reviewer needs a way to satisfy it.
1 Like