docs: Revamp OAuth 2.0 guide with PKCE flow, examples, and troubleshooting#21
Merged
osamasayed merged 1 commit intomainfrom Sep 23, 2025
Merged
docs: Revamp OAuth 2.0 guide with PKCE flow, examples, and troubleshooting#21osamasayed merged 1 commit intomainfrom
osamasayed merged 1 commit intomainfrom
Conversation
examples, and troubleshooting - Replaced old high-level OAuth 2.0 overview with step-by-step Authorization Code + PKCE flow. - Added clear separation between Content API (Client Credentials) and User API (Auth Code). - Included ready-to-run examples in Python (requests) and Node.js (axios). - Documented PKCE helper utilities (Node, Python). - Added example authorization URL, token exchange (public vs confidential), and refresh token flows. - Clarified required headers for User API calls (x-auth-token, x-client-id). - Added environment base URLs for Pre-Production vs Production. - Documented important considerations (redirect URI matching, state/nonce usage, scope usage). - Added common issues & troubleshooting table.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
osamasayed
approved these changes
Sep 23, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR fully rewrites the OAuth 2.0 documentation for Quran.Foundation APIs to be clearer, developer-friendly, and aligned with our Quick Start style.
The new guide emphasizes Authorization Code + PKCE for User APIs, while distinguishing it from Client Credentials for Content APIs.
Key changes
Motivation
The old guide was abstract and difficult to follow. This version: