Support generating personal access keys for calling API directly
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 729
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
Pro users have the need to directly invoke the Refly API within their workflow or application. At present, the API authentication mechanism requires the use of cookies, which can be rather cumbersome and inconvenient for API calls.
Describe the solution you'd like
Allow users to generate personal access keys (tokens) in the Settings panel.
With these generated tokens, users can directly call the Refly APIs, and the tokens will serve as the means of authentication, thereby streamlining the authentication process.
Describe alternatives you've considered
None.
Additional context
These personal access tokens should be encrypted properly in the database. After initial generation, users won't be able to see the plain token again from the interface.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing cookie-based API authentication flow and the Settings panel. Define the generation and one-time display behavior for personal access tokens, then verify that direct API calls authenticate with them and that stored tokens are encrypted and never shown in plain text again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, authentication, backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100