New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API #23
Comments
What's the idea around fleshing it out? What service/info is wanted? Or just to make bulk more useful? I'd suggest versioning the api if it is something you want to adopt for the project long term (e.g. .../api/1.0/...), I guess it depends what the goal of the api is! |
Nothing really wants this at the moment, it just seems like it could be useful to have around. An idea stemming from, https://trac.torproject.org/projects/tor/ticket/9529#comment:20 The fleshing out is to determine what info we have and how to expose it. Something like,
There are other services, besides the TBB, that depend on check, so long term support is a goal. See https://trac.torproject.org/projects/tor/ticket/10183 I'd rather not have the version number in the url. That can be accomplished with an |
Seems sound, how about RESTful-ish /api/ip/-ip-/-port- It could be useful to provide a lastseen timestamp for the IP lookups so consumers can make their own decisions for how many hours they're willing to allow true/false for instead of providing true/false? (or could be additional?) If no port is given, we could return the accept/reject policies? (Since isTor can't be known for that?)
Perhaps /api/router? Again, might want to provide ip/time combos?
So this is an exit list basically? , (I think we can drop the /all , no query implies all) Would providing microdesc/fulldesc endpoints be overkill? Any consumer should probably be using the fingerprints to lookup atlas/globe/whatever for further information? Perhaps supplying a 'further info' link we can update to the service of the day might be useful?
I don't feel that strongly about implementation on that as long as it's there :) But I would note that having it in the url makes it easier to test in browser (not a big issue really) On another aesthetic note: I noticed in the code it's looking for format=json, /i/like/endpoint.{json,xml,...} personally :) |
I started working on an API,
https://check.torproject.org/api/bulk?ip=38.229.72.19&port=443
This needs to be further fleshed out and documented.
The text was updated successfully, but these errors were encountered: