keybase / keybase/keybase-issues
user lookup api returns bad list value instead of null
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
When I call the user lookup API, some keybase user accounts cause api to return an error like below, instead of Null.
status
code 100
desc "bad list value"
fields
usernames "bad list value"
name "INPUT_ERROR"
A sample api call URL returning error is like this:
https://keybase.io/_/api/1.0/user/lookup.json?usernames=keybase_neverbackdown&fields=pictures,basics,proofs_summary
Some other usernames causing same error are acc0unt1 and nokeybaseusername.
As per your api documentation if a user is not found it should return Null without an error, like this one:
https://keybase.io/_/api/1.0/user/lookup.json?usernames=aasdads1231aas&fields=pictures,basics,proofs_summary
Contributor guide
No contributing guide indexed for this repository
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 with the user lookup endpoint examples in the issue, especially the requests for keybase_neverbackdown, acc0unt1, nokeybaseusername, and aasdads1231aas, and compare their responses. Done means nonexistent users consistently return null as documented instead of a "bad list value" input error.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100