dj-rest-auth vs. django-allauth headless API

[gleniat]

I've been using django-rest-auth and dj-rest-auth together with django-allauth for years, but recently noticed that django-allauth itself now provides a headless API.

Could anyone clarify what advantages there are today for choosing to use dj-rest-auth alongside allauth rather than using allauth alone when starting fresh with new Django implementations?

Possible reasons I see:

• Simpler API (fewer features to configure)
• No need to reimplement authentication logic if you're already using dj-rest-auth

To summarize, is dj-rest-auth still beneficial for new projects today, or would directly using django-allauth's native API generally be sufficient?

Thank you!

[stevelacey]

I don't have experience with headless, but my impression when I tried it and made this decision was that it's way more complicated than dj-rest-auth, and that's why I went this way – headless may well support more things – but it seemed quite far from a drop-in solution without consuming a lot of documentation and doing a lot of configuration.