# Mobile sign-in via deep-linking?

**URL:** <https://forum.ghost.org/t/mobile-sign-in-via-deep-linking/56314>\
**Category:** Developer help\
**Created:** [March 24, 2025, 4:07pm UTC](https://forum.ghost.org/t/mobile-sign-in-via-deep-linking/56314 "2025-03-24T16:07:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Wade\_Walker](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/wade_walker/32/35302_2.png) [@Wade\_Walker](https://forum.ghost.org/u/Wade_Walker)\
**Post date:** [March 24, 2025, 4:07pm UTC](https://forum.ghost.org/t/mobile-sign-in-via-deep-linking/56314/1 "2025-03-24T16:07:15Z")

</div>

Is it possible that member sign-in could work with a mobile app?  
I work on a mobile app that fetches and displays articles.  
How do members sign-in on this mobile app?  
The sign-in email goes directly to ghost.  
Is there a way to change this sign-in link so that it works with a deep-link to a mobile app that handles sign-in?

Any help appreciated!

---

<div class="post-metadata">

**Author:** ![Cathy\_Sarisky](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/cathy_sarisky/32/25750_2.png) [@Cathy\_Sarisky](https://forum.ghost.org/u/Cathy_Sarisky)\
**Post date:** [March 24, 2025, 5:05pm UTC](https://forum.ghost.org/t/mobile-sign-in-via-deep-linking/56314/2 "2025-03-24T17:05:32Z")

</div>

The sign-in link sending is baked into Ghost and happens when there’s a request to the send\_magic\_link endpoint. But you can also create members and get a sign in link via the Admin API. \*\*

I guess the question is, how do members using your app prove who they are, prior to getting logged in? You might think about doing OAuth with some provider. Sign in with Google probably won’t work in your app, but Facebook, Amazon, LinkedIn, Github, and others are fairly straightforward.

\*\* An admin API key cannot go into the app, for risk of exposure. You’ll need a server or cloud function somewhere that keeps your key safe. I’m sure you know this, but just in case…

(edit: fixed a typo)

---

<div class="post-metadata">

**Author:** ![Wade\_Walker](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/wade_walker/32/35302_2.png) [@Wade\_Walker](https://forum.ghost.org/u/Wade_Walker)\
**Post date:** [March 25, 2025, 1:17am UTC](https://forum.ghost.org/t/mobile-sign-in-via-deep-linking/56314/3 "2025-03-25T01:17:03Z")

</div>

> …get a sign in link via the Admin API. \*\*

Thanks for the quick reply!  
However, I’ve looked at the documentation. I apparently am missing something obvious. Can you please point me to the documentation that explains how to get a sign in link via the admin API for members (not users)?

---

<div class="post-metadata">

**Author:** ![Cathy\_Sarisky](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/cathy_sarisky/32/25750_2.png) [@Cathy\_Sarisky](https://forum.ghost.org/u/Cathy_Sarisky)\
**Post date:** [March 25, 2025, 1:26am UTC](https://forum.ghost.org/t/mobile-sign-in-via-deep-linking/56314/4 "2025-03-25T01:26:14Z")

</div>

My best tip for dealing with the api is always to do the action from the Ghost admin panel and see what it does, keeping the browser’s network tab open. In this case, you’re looking for the ‘impersonation’ link in the gear on an individual member’s page. You can hit that same endpoint with an admin jwt (made using an admin api key), getting a signin\_url that you can use to get the user logged in with a cookie.

Source: I made that possible: [Sign-in changes are afoot](https://www.spectralwebservices.com/blog/sign-in-changes-afoot/#item-2-memberssigninurls-endpoint-updated)

And no, you probably aren’t missing anything obvious. There are a number of undocumented endpoints.
