docs(auth): fix /verify endpoint documentation to match validation logic#2381
docs(auth): fix /verify endpoint documentation to match validation logic#2381rajpohekar wants to merge 1 commit intosupabase:masterfrom
Conversation
|
No actionable comments were generated in the recent review. 🎉 📝 WalkthroughSummary by CodeRabbit
WalkthroughThe README.md documentation has been updated to clarify the POST /verify and GET /verify verification methods. The changes replace a previous multi-type description with two mutually exclusive verification approaches: one using token with email/phone fields, and another using token_hash. Updates include explicit field requirements, validation rules, a new magiclink token_hash example, inclusion of email in the POST /verify token payload, and adjustments to the GET /verify description noting that the token query parameter is treated as token_hash internally. Minor wording changes were also made to the backward compatibility note. Tip Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord. Comment |
What changed
POST /verifydocumentation to reflect actual validation rulestoken+email/phonetoken_hashemail,phone,token_hash)typevaluesGET /verifybehavior wheretokenis treated as atoken_hashWhy
The existing README described request payloads that do not match the current
validation logic in
internal/api/verify.go, which results in confusingvalidation_failederrors for users following the docs.This PR aligns the documentation with the implementation without changing any
runtime behavior.
Scope