Deeplinking to Ring app

Ring Q&A
1

Hello!

Our team is trying to understand how best to link from our app into the Ring app store, ideally directly to our app’s page in the Ring app store. Is a deeplinking URL scheme available - either to the website, or directly into the iOS / Android app?

Currently we are just using https://account.ring.com/account/integrations - wondering if that is the best option at the moment.

Thanks,

Cam

2

Hi @cam_hill , Thanks for reviewing the Ring Appstore capabilities. Could you clarify the end-user experience you’re aiming to create?

For example, would a Ring customer discover your app in the Ring Appstore, click on it, and then be directed to your app’s homepage in a separate browser tab?

3

Hi Dinesh,

I’m thinking about at least 2 specific end user experiences:

  1. A user organically finds our app in the iOS/Android App Stores. We have a feature highlight that says “Connect to a ring camera”. Ideally that feature highlight button would like directly to the Ring integrations page where they can link a ring device to our app (rather than generically linking to the Ring app/website).

2. A user of our app has a Ring account with or without devices. We have a link to “Manage in Ring” to direct a user to manage their linked account (add/remove devices, etc.). Similarly, in this case ideally we’d take them directly to our app’s integration page rather than a generic page.

4

1. Deep linking from App Store feature highlights: You can direct users to your specific app’s integration page on Ring AppStore using this format: https://ring.com/pages/appstore/[your-app-name]. This takes users directly to your Ring integration page instead of a generic landing.

2. “Manage in Ring” account linking: This functionality already exists! We provide an account link URL that redirects authenticated users to your partner-specific page. In the Ring developer portal, you see a “Go to App” option that takes them directly to your integration page within Ring. This leverages the same differentiation we built into the Developer Portal between 3P app homepage and your app’s corresponding Ring pages.

1 Like
5

I have been trying this deeplink, but whenever I go to it I get a 304 error. I can get to it in my browser when I a logged in, so I think I must need some kind of headers to go to it? Authorization? Please help me understand this.

6

I’m seeing the same issue, but in my case it is a 404, not a 304.

The URL works only when I’m already logged in and have navigated to the page through Ring. If I copy the URL and open it directly, or try it from a fresh browser/session, it fails:

https://ring.com/pages/appstore/[app-name]

So it looks like /pages/appstore/[app-name] is not behaving like a public deeplink, or maybe the app slug needs to be configured/published differently.

Can someone from Ring clarify whether these URLs are supposed to work publicly, or only for authenticated users with an active session? If they require authentication, is there a supported URL format that redirects users through login and then lands them on the partner-specific app page?

7

Hi both,

Thanks for reaching out, I got confirmation from the team on this. The deep link (https://ring.com/pages/appstore/[app-name]) does work for signed-out users, so authentication is not the issue here.

What’s actually happening:

If your app is still in staging and the user (or browser session) is not allowlisted as a staging user in the Developer Portal, the page will return a 404. The URL is valid, but the app isn’t visible to anyone outside your approved staging testers.

This explains both behaviors:

  • It works when you’re logged in and navigating through Ring, because you’re likely signed in with an account that’s allowlisted as a staging user.
  • It returns 404 (or 304 in some caching scenarios) from a fresh session or different account, because that session isn’t on the allowlist.

How to fix:

  • If you need others to access the page during staging, add them as staging users in the Developer Portal (Test section — up to 10 staging users).
  • Once your app is published (beta, gradual, or full rollout), the deep link will resolve publicly for any user without needing allowlisting.

So nothing is misconfigured on your end, the URL format is correct, it’s just gated to allowlisted users while in staging. Once you’re through certification and published, it’ll work as a public deep link.

Hope that clears it up!

8

Thanks Shay — that does help explain part of what we were seeing, but I still think there may be another issue with the actual user flow we’re trying to support.

In our case, the user starts inside our app. They’re authenticated with us, but they may not already have an active Ring browser session. When they tap something like “Connect Ring” or “Add Ring,” we redirect them to:

https://ring.com/pages/appstore/[app-name]

What we’re seeing is that the URL returns a 404 instead of redirecting the user through Ring login and then landing on the app page afterward.

Also, just to clarify, the Ring account I’m testing with is added as a staging user in the Developer Portal, and linking works correctly when I go through the normal Ring app flow. So staging access itself seems fine.

The issue seems specifically tied to opening the deeplink directly from our app when there isn’t already an active Ring session in the browser.

Is there a different URL or supported flow intended for this scenario? Ideally we’d want users to be prompted to log into Ring if needed, and then continue on to the partner-specific integration page afterward.

I do understand that once we are out of staging, the deep link will be public, but I want to know how to test it before we are out of staging.

9

Hi Darrell,

Thanks for the detailed follow-up, this is helpful context and here’s what we’ve confirmed:

The issue: The direct deep link (https://ring.com/pages/appstore/[app-name]) does not currently handle the unauthenticated-to-login redirect gracefully. If the user doesn’t have an active Ring session in the browser, it returns a 404 rather than prompting them to log in and then forwarding them to the app page. We agree this isn’t ideal for the flow you’re describing

What to do in the meantime:

Redirect your users to Ring Appstore | Ring instead. From there, they’ll be prompted to log in if needed, and once authenticated they can view your staging app and initiate the connection. Since your Ring account is already added as a staging user, the app will be visible and the linking flow will work as expected from that page.

It’s not the seamless single-link experience you’re after, but it unblocks your testing while in staging.

Going forward:

We’ve flagged this as something that needs to be fixed…the direct app deep link should handle the unauthenticated case by redirecting through login and then landing the user on the correct app page. We’ll be investigating improvements to support this flow properly. No timeline to share yet, but it’s on our radar.

Thanks for raising this! It’s good feedback and will help us improve the experience for partners building this kind of in-app integration flow.

1 Like