# \#authorization-flow
**URL:** https://community.auth0.com/tag/authorization-flow/1062.md
[Latest](https://community.auth0.com/latest.md) · [Categories](https://community.auth0.com/categories.md) · [Tags](https://community.auth0.com/tags.md)
---
## [Introducing IdentiFlows.dev: A Visual Reference for Identity Flows](https://community.auth0.com/t/introducing-identiflows-dev-a-visual-reference-for-identity-flows/203773)
**Author:** [@andrea.chiarelli](https://community.auth0.com/u/andrea.chiarelli)\
**Replies:** 1\
**Last updated:** [September 29, 2026, 3:01pm UTC](https://community.auth0.com/t/introducing-identiflows-dev-a-visual-reference-for-identity-flows/203773 "2026-09-29T15:01:29Z")
If you are a visual learner or you would like to have authorization and authentication flow diagrams at hand, the identiflow.dev website is for you. Read this blog post to learn more.
---
## [Using Code Grant with SPA + REST API](https://community.auth0.com/t/using-code-grant-with-spa-rest-api/18632)
**Author:** [@jon3](https://community.auth0.com/u/jon3)\
**Replies:** 1\
**Last updated:** [December 30, 2018, 10:09pm UTC](https://community.auth0.com/t/using-code-grant-with-spa-rest-api/18632 "2018-12-30T22:09:58Z")
(Possible duplicate of SPA with Authorization Code Grant, but the wording in that post is a little ambiguous) Our web app is a staticly served SPA that makes calls to a backend REST API for all of its data. We used to u…
---
## [Twiitter API breaking change to OAuth flow](https://community.auth0.com/t/twiitter-api-breaking-change-to-oauth-flow/8730)
**Author:** [@gurpreet](https://community.auth0.com/u/gurpreet)\
**Replies:** 0\
**Last updated:** [November 13, 2017, 6:00pm UTC](https://community.auth0.com/t/twiitter-api-breaking-change-to-oauth-flow/8730 "2017-11-13T18:00:21Z")
!\[alt text\]\[1\] A change needs to be made in Auth0 to handle this breaking change, otherwise the Authorization screen will keep appearing everytime someone tries to login using twitter. Gurpreet