keybase / keybase/keybase-issues
API: Support key_id query param
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
In lookup/discover, add support for key_ids.
Currently I am doing a key fetch and then looking up users by key_fingerprint. Would be nice to skip the key fetch step. (BTW, this is for use case for looking up recipients of a message from key_ids used to encrypt, not signing or verifying, which I get the fingerprint from kbpgp a-ok.) Low priority, but nice to have.
```
https://keybase.io/_/api/1.0/user/lookup.json?key_id=0022045e363bcbc1,401ed93c8a2c0cf0
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the lookup/discover API endpoint and compare its current key_fingerprint handling with the key_id query example in the issue. Done means callers can pass one or more key IDs to look up recipients directly, without first fetching keys; the payload does not name implementation files or tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100