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
Query organization on dev.to/api #9212
Comments
|
Thanks for the issue! We'll take your request into consideration and follow up if we decide to tackle this issue. To our amazing contributors: issues labeled To claim an issue to work on, please leave a comment. If you've claimed the issue and need help, please ping @thepracticaldev/oss and we will follow up within 3 business days. For full info on how to contribute, please check out our contributors guide. |
|
I think the URL structure should be something like:
If someone tackles this I strongly recommend to send separate PRs for each endpoint and keep the API spec file updated as well. |
|
I can work on this |
|
I've assigned you the issue, thanks @twinsfan421 ! |
|
@rhymes I am working on it and have couple questions. |
Yes, that's probably a good idea. It should mirror https://docs.dev.to/api/#operation/getUser.
Rough rule of thumb that the current API seems to follow: if it's public information, no authentication is needed. Best to follow similar API endpoints for now, the API docs are a good reference for this: https://docs.dev.to/api/ |
|
Hey @twinsfan421 thanks so much for all the contributions to this so far. Given the current PRs that have already been merged is there anything else left for this issue? I don't want to pull you off of this issue if you are close to finishing up any other tasks. |
This issue is completed. Thank you |
|
Thanks for the confirmation and thanks again for all the work you did on this. We really appreciate it 🙏🎉 |
Feature Request
Currently there in no way to query an organization on dev.to/api
Describe the solution you'd like
It would be nice to query https://dev.to/api/organization/articles, https://dev.to/api/organization/users, https://dev.to/api/organization/listings where organization is e.g., https://dev.to/api/vetswhocode
The description could read:
The text was updated successfully, but these errors were encountered: