# Implement discourse Apple login using API

**URL:** https://meta.discourse.org/t/implement-discourse-apple-login-using-api/286700
**Category:** Development
**Tags:** apple-auth
**Created:** [November 27, 2023, 8:49am UTC](https://meta.discourse.org/t/implement-discourse-apple-login-using-api/286700 "2023-11-27T08:49:50Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [December 4, 2023, 10:49am UTC](https://meta.discourse.org/t/implement-discourse-apple-login-using-api/286700/5 "2023-12-04T10:49:21Z")

</div>

I’m afraid there’s no easy answer. Authentication APIs like this are specifically designed to avoid them being triggered without real user interaction on the web.

For your use case, the more common solution would be to use the [user API keys](https://meta.discourse.org/t/user-api-keys-specification/48536) system. That will allow Discourse to handle 100% of the authentication logic, and will give your app some per-user API keys. That strategy should be much more robust than trying to ‘fake’ a user session.

---

_[View the full topic](https://meta.discourse.org/t/implement-discourse-apple-login-using-api/286700)._