API Support

@ossamaweb we are currently working on internal changes to reviews. They will be added to the API post that.

@ossamaweb I'm afraid not and we do not plan to expose that information.

@dhruvparmar Thanks. I'll figure something out. I see that the order of media in the API is different than that on the website. is that bug or website uses some type of sorting?

@sarunw hey, that's a good suggestion. I'll update here once we implement that.

@vsnthv Currently we don't allow upvotes via the API. The access_token is long lived(never expires) and access_grant_token expires in 20m.

@imknight hey, you can filter "goals" by using "completed" flag here http://api-v2-docs.producthunt.c... Setting `completed: true` on the query will result in only completed goals being fetched.

@dhruvparmar Got it , i use Viewer to check, is a bit funny, when checking own goal cannot filter by using completed flag

@imknight I've approved write access for your application. Let me know incase you're facing issues with mutations still.

@dhruvparmar Seems like doing a "goals" query keeps returning a 204 (no content) for me. It works fine from the API explorer, but any call to this endpoint from my code succeeds but doesn't return anything. Any idea on what may be up with this? EDIT: This has now been resolved on the server-side.

@dhruvparmar This is great stuff, thanks!

@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.

@akshay_ashok1 Checkout step 2 here https://github.com/producthunt/p...

@dhruvparmar Amazing job!

@dhruvparmar I can't figure out the client Credential token part

@ossamaweb @asingh2 @dhruvparmar Awesome, is this also reflected in the API explorer?

@asingh2 @dhruvparmar Awesome! Thanks man ;)

@dhruvparmar thanks for add Goal Create, how about Project Create ? will it be added ?

@imknight We wouldn't be adding project create as of now. I'll keep you updated here incase something changes.

@ossamaweb @wayfarerish @raghuv_adhepalli @roy_shao @dhruvparmar This is brilliant, thank you!

@dhruvparmar thanks! :)

@wayfarerish @dhruvparmar Any plan for isCheer?

@nikolay_siabrenko @dhruvparmar Great job! Would it be possible to provide votes as query? The use case I am thinking of is to trigger an action when a post reaches a certain amount of upvotes. II do not want to track the number of upvotes for a specific post but for all posts - for example show post on a webpage once it reaches 100 upvotes.

@janzikan hey, we do not plan on exposing "votes" on the root query, as "votes" should always be fetched in the context of a Votable type. For your use case I'd suggest going with something like this 1. Fetch posts ordered by VOTES everyday 2. Filter out posts which could hit the threshold (100 in this case) and trigger polling the "post(id: postId)" field for them. I know this is not ideal, but probably something that could work. Don't worry about the number of requests as we can increase your rate limit quotas if you start getting blocked by them.

@dhruvparmar Better solution would be to be able to filter posts that have upvotes count greater than X and to order them by VOTES but in descending order. Are you planning to implement option for ordering so we choose whether the results should be ordered in ascending or descending order? Are you planning to implement filtering for the queries?

@janzikan the VOTES option sorts posts in descending order of votes count currently. We don't have plans to add filtering for the votes query as of now. Regarding ability to define the sort order, we'll try to incorporate this into the API. I'll share an update here once it's implemented.

@wayfarerish hey, both the code and access token are unique for each user. Currently access tokens are long lived i.e they do not expire. Whenever a user authorises your application you get an access token which you can use to make authenticated requests to the API. Incase you loose the access token you can always re-request it by hitting the "v2/oauth/authorize" endpoint again as most likely the grant code would have expired by then.

@dhruvparmar thanks :)

@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 thank you! :)

@wayfarerish i'm not sure about this, will have to get back to you on this. cc @devladinci

@wayfarerish hey "clientMutationId" is a unique identifier used to track the mutation. In most cases this is not required so you can ignore it. Read more here https://facebook.github.io/relay...

@dhruvparmar thank you!

@wayfarerish hey, the default page size for all connections is 20. You might be getting 19 if total goals are < 20 (depending on the connection filter params). The 'current' flag is set when a user goes into focus mode for a Goal. You should be able to try that out in the extension here https://chrome.google.com/websto...

@dhruvparmar thanks, will check that out...then I think it *might* be an edge case bug because I randomly get 19/20 when I have exactly 20 goals 🤔

@wayfarerish will try to answer point by point 1. Yes there will be update published here once `GoalCreate` mutation is supported. You can view all goals of a user already by using `userId` filter here http://api-v2-docs.producthunt.c... 2. Currently you can only fetch those for the logged in/authenticated user i.e 'viewer'. Check here for details http://api-v2-docs.producthunt.c... 3. 'isMaker' represents whether the User has been added as a maker for any of the posts on ProductHunt. I think the naming is confusing and we'll probably change the field name soon. 4. As of now ability to comment on a goal and ability to "cheer" are not part of the API plans. We might consider exposing those later on. Again there will be an update published here regarding same.

@dhruvparmar thank you :)

@charltoons hey, the rate limits apply to the entire application. Unfortunately we do not plan on supporting web-hooks for now. I'd suggest to go with the polling option and you can use "goals" connection to fetch the goals. You could use "userId" & "completed" filters here http://api-v2-docs.producthunt.c... Incase you are getting blocked by rate limits please write to hello@producthunt.com with your API Key and we will bump up the rate limit quota for your application.

@producthunt @dhruvparmar Ok sounds good. Thanks!

@dhruvparmar @ossamaweb Yeah I agree. A link to product videos would be handy too. Hope we can get access to this.

@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?