@dhruvparmar I see some planned updates to APIs here and see recent changes on github. Will the docs be updated asap or do we need to keep an eye here and on github?
@wayfarerish hey, any updates to the GraphQL interface of the API will always reflect in the reference here http://api-v2-docs.producthunt.c...
Unfortunately we don't have a change-log yet so we've decided to publish those updates here as well for the Makers festival participants.
@dhruvparmar Hey, amazing job on the GraphQL API. Are you guys going to add more fields to the post query? I need the post makers and images also reviews would be great ;)
@ossamaweb@asingh thanks for feedback guys 🙌. We should be able to add those fields to Post query. I'll update here once they are added. Would be good if you could elaborate how you'd be using them in your respective applications?
Hey everyone! Dhruv from the engineering team at Product Hunt. The new version for the Product Hunt public API is built using GraphQL. We want you to have a smooth experience while integrating with the API and I'll be here to assist you in any issues that might arise.
Here are some quick tips to get started:
1. To explore the GraphQL interface of the API quickly, you can use the GraphiQL Explorer app.
2. We've published a minimal Node + React App as a starter kit on Github here.
Happy Hacking 💻🚀!
Report
@dhruvparmar I'm trying minimal Node + React App as a starter kit, but on clicking Login with product hunt, it get redirected to /authorize but nothing seems to happen. also there is this POST http://localhost:3001/graphql 404 (Not Found) in console.
@akshay_ashok1 Hey, please make sure to copy `.env.sample` file and rename it to `.env` file in your project root. Also update all `PH_` variables in the `.env` file to appropriate values. I'm guessing there is an issue with the environment variables.
Report
@dhruvparmar I can't figure out the client Credential token part
@dhruvparmar Facing this error on POST request Use the access grant code you received through the redirect to request an access token
error:"invalid_grant"
error_description:"The provided authorization grant is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client."
@yhdesai hey, The "invalid_grant" issue is most likely due to an invalid `code` being used to request the access token.
Regarding the starter kit, the get access token part is executed here https://github.com/producthunt/p... once the user authorizes your application.
Incase you are looking to build a client only application and do not need users to authorize it you can check out this codesandbox https://codesandbox.io/s/phapi20... as well.
@dhruvparmar@yhdesai I was facing this issue earlier too, which I resolved through ensuring that the redirect_uri in both the authorise and token calls matched.
Report
@dhruvparmar@yhdesai@jpeguin1 I am trying the same endpoint using v2 and it still throws this error. The code and redirect_uri are correct. What might be wrong?
@ossamaweb we are currently working on internal changes to reviews. They will be added to the API post that.
Report
@dhruvparmar Hey Dhruv. Will you guys support stuff like upvoting, commenting, updating user information, etc. through API v2, or is this Makers Festival only focused on maker goals?
@evrimfeyyaz Hey, there are no plans to add upvoting or commenting as of now. We would be adding updating user information at a later stage. For now we are focusing on adding write functions related to maker goals.
Report
@dhruvparmar Is it possible to use API v1 for the stuff that are not supported in v2?
@evrimfeyyaz no since write capabilities in both the versions differ, you would not be able to use v1 endpoints with a v2 application. Also we will soon drop support for v1 API so would be better to build with v2.
Report
@dhruvparmar I would really like to use v2, but unfortunately it is very limited for the idea I had. If you are dropping support for v1 without porting the full functionality to v2, does that mean that many of the apps that were built on v1 will stop working with no way to rewrite them in v2?
@evrimfeyyaz we would definitely give a time buffer for developers to migrate apps to v2 before dropping support for v1. Also we might consider adding some of v1's write capabilities depending on the use case.
As for the Makers festival scope, all apps need to be using v2 API and we wouldn't be adding commenting or upvoting on posts for now.
Report
@dhruvparmar
While trying to retrieve list of product hunt 'Posts' all the 'media' objects are coming as null even though the products have videos or images or both.
More Details :--
Here is the query which I fire.
Query : To retrieve posts order by votes.
{
posts (order: VOTES) {
edges{
node{
id,
name,
media{
type,
videoUrl
}
}
}
}
}
Result : Trimmed part the the corresponding response.
{
"data": {
"posts": {
"edges": [
{
{
"node": {
"id": "76",
"name": "Slack",
"media": [
{
"type": "video",
"videoUrl": null
},
{
"type": "image",
"videoUrl": null
},
{
"type": "image",
"videoUrl": null
},
{
"type": "image",
"videoUrl": null
},
{
"type": "image",
....
.
.
.
.
@vaibhav_soulskill hey, the "videoUrl" specifically only fetches URL for the video if present. Can you try adding "url" field to the "media" object as well? That should give you links to images for all media items.
I've tried running the above query and seems there is a bug with "videoUrl" generation in the API. We'll try and patch it up as soon as possible.
Report
@dhruvparmar Sounds cool, My use-case requires videoUrl so I will be waiting for it.
Replies
Makerbox for Product Hunt
YourStack
Makerbox for Product Hunt
NewsletterStash
TulaByte
YourStack
@ossamaweb @asingh @dhruvparmar
any update on the data fetching post makers or users of comments on the post.
and also review.
YourStack
YourStack
YourStack
YourStack
Bulletin
Scout
Makerbox for Product Hunt
YourStack
YourStack
Screenshot Studio
Shipr Labs
Shipr Labs
Shipr Labs
YourStack
Bulletin
NewsletterStash
YourStack
YourStack
YourStack
YourStack
YourStack
YourStack