-
-
Notifications
You must be signed in to change notification settings - Fork 488
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Easier way to retrieve user device_key for integrations #295
Comments
Hi there, You can add your service to the user’s app using a URL Scheme.
(You can also simply forward the requests to the Bark-Server.) URL Scheme:
or
Once the user clicks the link and successfully adds the server, your server will receive a register request. |
Hey! @Finb 👋 I'm running the Bark server on my VPS using Docker, and I'm trying to better understand how the After the user clicks Is there any way for my backend to receive this information (like the If there's a recommended approach, could you show an example of how to handle this in Node.js? Thanks! 🔥 |
An untested but potentially feasible solution:
Then, provide users with the URL Scheme:
|
Hi there! 👋
I'm working on integrating Bark into my own backend system to send push notifications to users.
I was wondering: is there currently an easy way to programmatically retrieve the user's device_key (the one used to receive notifications), similar to a “plug-and-play” integration?
Ideally, I’d like to let the user connect Bark to their account without needing much interaction inside the mobile app — for example, using a webhook or a callback after tapping a notification.
Does anything like this exist or is planned? Or would you recommend any best practices for this kind of user onboarding flow?
Thanks in advance for your awesome work on Bark! 🚀
The text was updated successfully, but these errors were encountered: