docs: improve shareable link protection bypass API documentation #140
Conversation
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
- Update main API documentation with clear use cases and examples
- Add comprehensive examples for create, revoke, and regenerate scenarios
- Explain the key insight that empty {} creates new shareable links
- Document common error patterns (409 conflicts)
- Add working code examples with error handling
- Create comprehensive API guide with troubleshooting
- Update model documentation with practical examples
Fixes confusion around when to use empty body vs revoke patterns.
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.
Fixes confusion around when to use empty body vs revoke patterns.
Feedback based on: https://vercel.slack.com/archives/C042LCH092M/p1749117014921879