So, some questions: 1. How long does the temporary code last? 10 secs, 10 mins? Does it time out while I format the request by hand? (I'm just testing right now.) 2. Is there a problem with the server code at Disqus that is generating this request? 3. How long are the access tokens good for? I would really like to allow the Users to authorize my app forever. I can't make them authorize the app every time they log in.
i don't have documentation, but during bug testing i halted the access_token request for at least 20 seconds before successfully sending it, i'd imagine the code is valid for a little while longer than that, but that really shouldn't be an issue.
regarding question 3, you should read the documentation a bit more(http://disqus.com/api/docs/auth/#response), the tokens are valid for 30days, but you can make an automated process that use the refresh token to request a new access_token without the user knowing.
On Fri, Nov 18, 2011 at 8:25 PM, djangok <kevincheval...@gmail.com> wrote: > I am able to retrieve the temporary code with /api/oauth/2.0/ > authorize/
> When I try to retrieve the Access Code from /api/oauth/2.0/ > access_token/, I receive HTTP 400: Invalid API Version.
> So, some questions: > 1. How long does the temporary code last? 10 secs, 10 mins? Does it > time out while I format the request by hand? (I'm just testing right > now.) > 2. Is there a problem with the server code at Disqus that is > generating this request? > 3. How long are the access tokens good for? I would really like to > allow the Users to authorize my app forever. I can't make them > authorize the app every time they log in.
> i don't have documentation, but during bug testing i halted the > access_token request for at least 20 seconds before successfully > sending it, i'd imagine the code is valid for a little while longer > than that, but that really shouldn't be an issue.
> regarding question 3, you should read the documentation a bit > more(http://disqus.com/api/docs/auth/#response), the tokens are valid > for 30days, but you can make an automated process that use the refresh > token to request a new access_token without the user knowing.
> On Fri, Nov 18, 2011 at 8:25 PM, djangok <kevincheval...@gmail.com> wrote: > > I am able to retrieve the temporary code with /api/oauth/2.0/ > > authorize/
> > When I try to retrieve the Access Code from /api/oauth/2.0/ > > access_token/, I receive HTTP 400: Invalid API Version.
> > So, some questions: > > 1. How long does the temporary code last? 10 secs, 10 mins? Does it > > time out while I format the request by hand? (I'm just testing right > > now.) > > 2. Is there a problem with the server code at Disqus that is > > generating this request? > > 3. How long are the access tokens good for? I would really like to > > allow the Users to authorize my app forever. I can't make them > > authorize the app every time they log in.
> The Invalid API Version error went away. Authentication works > perfectly now.
> I am encountering an error when trying to use the refresh request you > pointed out to me.
> If I try to make a request like the documentation specifies, the API > refuses it, saying redirect_uri is a missing parameter.
> If I give it the same redirect_uri as the rest of my authentication > system, it redirects with ?error=unsupported_response_type appended to > the end.
> If I pass it response_type=code, then it returns the regular "Would > you like to authorize this app to edit your Disqus forum" page, which > isn't good.
> Is there a response type that I should pass into the GET request that > I don't know of?
> Kevin
> On Nov 19, 5:23 am, Michael HP <wus...@gmail.com> wrote:
> > i don't have documentation, but during bug testing i halted the > > access_token request for at least 20 seconds before successfully > > sending it, i'd imagine the code is valid for a little while longer > > than that, but that really shouldn't be an issue.
> > regarding question 3, you should read the documentation a bit > > more(http://disqus.com/api/docs/auth/#response), the tokens are valid > > for 30days, but you can make an automated process that use the refresh > > token to request a new access_token without the user knowing.
> > On Fri, Nov 18, 2011 at 8:25 PM, djangok <kevincheval...@gmail.com> wrote: > > > I am able to retrieve the temporary code with /api/oauth/2.0/ > > > authorize/
> > > When I try to retrieve the Access Code from /api/oauth/2.0/ > > > access_token/, I receive HTTP 400: Invalid API Version.
> > > I've checked to make sure the format was correct. I tried it with > > > curl on the command line, and with the python code supplied by Disqus. > > > (https://github.com/disqus/disqus-api-demos/tree/master/comments) > > > Both return the same response.
> > > So, some questions: > > > 1. How long does the temporary code last? 10 secs, 10 mins? Does it > > > time out while I format the request by hand? (I'm just testing right > > > now.) > > > 2. Is there a problem with the server code at Disqus that is > > > generating this request? > > > 3. How long are the access tokens good for? I would really like to > > > allow the Users to authorize my app forever. I can't make them > > > authorize the app every time they log in.
> Hopefully the doc can be updated so others won't be confused.
> On Nov 20, 11:03 pm, djangok <kevincheval...@gmail.com> wrote: > > Ok, thank you for the response.
> > The Invalid API Version error went away. Authentication works > > perfectly now.
> > I am encountering an error when trying to use the refresh request you > > pointed out to me.
> > If I try to make a request like the documentation specifies, the API > > refuses it, saying redirect_uri is a missing parameter.
> > If I give it the same redirect_uri as the rest of my authentication > > system, it redirects with ?error=unsupported_response_type appended to > > the end.
> > If I pass it response_type=code, then it returns the regular "Would > > you like to authorize this app to edit your Disqus forum" page, which > > isn't good.
> > Is there a response type that I should pass into the GET request that > > I don't know of?
> > Kevin
> > On Nov 19, 5:23 am, Michael HP <wus...@gmail.com> wrote:
> > > i don't have documentation, but during bug testing i halted the > > > access_token request for at least 20 seconds before successfully > > > sending it, i'd imagine the code is valid for a little while longer > > > than that, but that really shouldn't be an issue.
> > > regarding question 3, you should read the documentation a bit > > > more(http://disqus.com/api/docs/auth/#response), the tokens are valid > > > for 30days, but you can make an automated process that use the refresh > > > token to request a new access_token without the user knowing.
> > > On Fri, Nov 18, 2011 at 8:25 PM, djangok <kevincheval...@gmail.com> > wrote: > > > > I am able to retrieve the temporary code with /api/oauth/2.0/ > > > > authorize/
> > > > When I try to retrieve the Access Code from /api/oauth/2.0/ > > > > access_token/, I receive HTTP 400: Invalid API Version.
> > > > I've checked to make sure the format was correct. I tried it with > > > > curl on the command line, and with the python code supplied by > Disqus. > > > > (https://github.com/disqus/disqus-api-demos/tree/master/comments) > > > > Both return the same response.
> > > > So, some questions: > > > > 1. How long does the temporary code last? 10 secs, 10 mins? Does it > > > > time out while I format the request by hand? (I'm just testing right > > > > now.) > > > > 2. Is there a problem with the server code at Disqus that is > > > > generating this request? > > > > 3. How long are the access tokens good for? I would really like to > > > > allow the Users to authorize my app forever. I can't make them > > > > authorize the app every time they log in.
On Sunday, November 20, 2011 10:03:31 PM UTC-7, djangok wrote: > Ok, thank you for the response.
> The Invalid API Version error went away. Authentication works > perfectly now.
> I am encountering an error when trying to use the refresh request you > pointed out to me.
> If I try to make a request like the documentation specifies, the API > refuses it, saying redirect_uri is a missing parameter.
> If I give it the same redirect_uri as the rest of my authentication > system, it redirects with ?error=unsupported_response_type appended to > the end.
> If I pass it response_type=code, then it returns the regular "Would > you like to authorize this app to edit your Disqus forum" page, which > isn't good.
> Is there a response type that I should pass into the GET request that > I don't know of?
> Kevin
> On Nov 19, 5:23 am, Michael HP <wus...@gmail.com> wrote: > > i don't have documentation, but during bug testing i halted the > > access_token request for at least 20 seconds before successfully > > sending it, i'd imagine the code is valid for a little while longer > > than that, but that really shouldn't be an issue.
> > regarding question 3, you should read the documentation a bit > > more(http://disqus.com/api/docs/auth/#response), the tokens are valid > > for 30days, but you can make an automated process that use the refresh > > token to request a new access_token without the user knowing.
> > On Fri, Nov 18, 2011 at 8:25 PM, djangok <kevincheval...@gmail.com> > wrote: > > > I am able to retrieve the temporary code with /api/oauth/2.0/ > > > authorize/
> > > When I try to retrieve the Access Code from /api/oauth/2.0/ > > > access_token/, I receive HTTP 400: Invalid API Version.
> > > I've checked to make sure the format was correct. I tried it with > > > curl on the command line, and with the python code supplied by Disqus. > > > (https://github.com/disqus/disqus-api-demos/tree/master/comments) > > > Both return the same response.
> > > So, some questions: > > > 1. How long does the temporary code last? 10 secs, 10 mins? Does it > > > time out while I format the request by hand? (I'm just testing right > > > now.) > > > 2. Is there a problem with the server code at Disqus that is > > > generating this request? > > > 3. How long are the access tokens good for? I would really like to > > > allow the Users to authorize my app forever. I can't make them > > > authorize the app every time they log in.
On Friday, June 29, 2012 at 2:33 PM, Vinney K wrote:
> Sorry to nudge an old post but I just can't seem to be able to make the access_token request work and I'm at a loss... I'm sending a post similar to:
> I keep receiving the error: Missing required parameter: grant_type
> Did you ever experience this issue? If so, can you share your solution?
> Thanks,
> Vinney
> On Sunday, November 20, 2011 10:03:31 PM UTC-7, djangok wrote:
> > Ok, thank you for the response.
> > The Invalid API Version error went away. Authentication works
> > perfectly now.
> > I am encountering an error when trying to use the refresh request you
> > pointed out to me.
> > If I try to make a request like the documentation specifies, the API
> > refuses it, saying redirect_uri is a missing parameter.
> > If I give it the same redirect_uri as the rest of my authentication
> > system, it redirects with ?error=unsupported_response_type appended to
> > the end.
> > If I pass it response_type=code, then it returns the regular "Would
> > you like to authorize this app to edit your Disqus forum" page, which
> > isn't good.
> > Is there a response type that I should pass into the GET request that
> > I don't know of?
> > Kevin
> > On Nov 19, 5:23 am, Michael HP <wus...@gmail.com> wrote:
> > > i don't have documentation, but during bug testing i halted the
> > > access_token request for at least 20 seconds before successfully
> > > sending it, i'd imagine the code is valid for a little while longer
> > > than that, but that really shouldn't be an issue.
> > > regarding question 3, you should read the documentation a bit
> > > more(http://disqus.com/api/docs/auth/#response), the tokens are valid
> > > for 30days, but you can make an automated process that use the refresh
> > > token to request a new access_token without the user knowing.
> > > On Fri, Nov 18, 2011 at 8:25 PM, djangok <kevincheval...@gmail.com> wrote:
> > > > I am able to retrieve the temporary code with /api/oauth/2.0/
> > > > authorize/
> > > > When I try to retrieve the Access Code from /api/oauth/2.0/
> > > > access_token/, I receive HTTP 400: Invalid API Version.
> > > > I've checked to make sure the format was correct. I tried it with
> > > > curl on the command line, and with the python code supplied by Disqus.
> > > > (https://github.com/disqus/disqus-api-demos/tree/master/comments)
> > > > Both return the same response.
> > > > So, some questions:
> > > > 1. How long does the temporary code last? 10 secs, 10 mins? Does it
> > > > time out while I format the request by hand? (I'm just testing right
> > > > now.)
> > > > 2. Is there a problem with the server code at Disqus that is
> > > > generating this request?
> > > > 3. How long are the access tokens good for? I would really like to
> > > > allow the Users to authorize my app forever. I can't make them
> > > > authorize the app every time they log in.
I have been trying that as well but, as you had first reported, when I remove all elements from the querystring, I get the invalid api version error. I've tried playing with different configurations where some elements are in the querystring and others are in the body but nothing has worked so far. Do you happen to remember what you did to make the api version error go away?
Also, does the content type matter? application/json vs. application/x-www-form-urlencoded vs. ....
On Friday, June 29, 2012 4:01:23 PM UTC-6, Anton Kovalyov wrote: > Hey,
> You need to send these params in your POST body not as a query string. > Sorry about confusion.
> Anton
> On Friday, June 29, 2012 at 2:33 PM, Vinney K wrote:
> Sorry to nudge an old post but I just can't seem to be able to make the > access_token request work and I'm at a loss... I'm sending a post similar > to:
> I keep receiving the error: *Missing required parameter: grant_type*
> Did you ever experience this issue? If so, can you share your solution?
> Thanks, > Vinney
> On Sunday, November 20, 2011 10:03:31 PM UTC-7, djangok wrote:
> Ok, thank you for the response.
> The Invalid API Version error went away. Authentication works > perfectly now.
> I am encountering an error when trying to use the refresh request you > pointed out to me.
> If I try to make a request like the documentation specifies, the API > refuses it, saying redirect_uri is a missing parameter.
> If I give it the same redirect_uri as the rest of my authentication > system, it redirects with ?error=unsupported_response_type appended to > the end.
> If I pass it response_type=code, then it returns the regular "Would > you like to authorize this app to edit your Disqus forum" page, which > isn't good.
> Is there a response type that I should pass into the GET request that > I don't know of?
> Kevin
> On Nov 19, 5:23 am, Michael HP <wus...@gmail.com> wrote: > > i don't have documentation, but during bug testing i halted the > > access_token request for at least 20 seconds before successfully > > sending it, i'd imagine the code is valid for a little while longer > > than that, but that really shouldn't be an issue.
> > regarding question 3, you should read the documentation a bit > > more(http://disqus.com/api/docs/auth/#response), the tokens are valid > > for 30days, but you can make an automated process that use the refresh > > token to request a new access_token without the user knowing.
> > On Fri, Nov 18, 2011 at 8:25 PM, djangok <kevincheval...@gmail.com> > wrote: > > > I am able to retrieve the temporary code with /api/oauth/2.0/ > > > authorize/
> > > When I try to retrieve the Access Code from /api/oauth/2.0/ > > > access_token/, I receive HTTP 400: Invalid API Version.
> > > I've checked to make sure the format was correct. I tried it with > > > curl on the command line, and with the python code supplied by Disqus. > > > (https://github.com/disqus/disqus-api-demos/tree/master/comments) > > > Both return the same response.
> > > So, some questions: > > > 1. How long does the temporary code last? 10 secs, 10 mins? Does it > > > time out while I format the request by hand? (I'm just testing right > > > now.) > > > 2. Is there a problem with the server code at Disqus that is > > > generating this request? > > > 3. How long are the access tokens good for? I would really like to > > > allow the Users to authorize my app forever. I can't make them > > > authorize the app every time they log in.
I'm literally about to give up hope on Disqus if I can't get this issue resolved within the next day or so. Support is slow at best and the documentation appears to be incorrect. This has been a very frusturating experience.
On Friday, June 29, 2012 5:44:09 PM UTC-6, Vinney K wrote: > I have been trying that as well but, as you had first reported, when I > remove all elements from the querystring, I get the invalid api version > error. I've tried playing with different configurations where some elements > are in the querystring and others are in the body but nothing has worked so > far. Do you happen to remember what you did to make the api version > error go away?
> Also, does the content type matter? application/json vs. > application/x-www-form-urlencoded vs. ....
> Thanks! > Vinney
> On Friday, June 29, 2012 4:01:23 PM UTC-6, Anton Kovalyov wrote:
>> Hey,
>> You need to send these params in your POST body not as a query string. >> Sorry about confusion.
>> Anton
>> On Friday, June 29, 2012 at 2:33 PM, Vinney K wrote:
>> Sorry to nudge an old post but I just can't seem to be able to make the >> access_token request work and I'm at a loss... I'm sending a post similar >> to:
>> I keep receiving the error: *Missing required parameter: grant_type*
>> Did you ever experience this issue? If so, can you share your solution?
>> Thanks, >> Vinney
>> On Sunday, November 20, 2011 10:03:31 PM UTC-7, djangok wrote:
>> Ok, thank you for the response.
>> The Invalid API Version error went away. Authentication works >> perfectly now.
>> I am encountering an error when trying to use the refresh request you >> pointed out to me.
>> If I try to make a request like the documentation specifies, the API >> refuses it, saying redirect_uri is a missing parameter.
>> If I give it the same redirect_uri as the rest of my authentication >> system, it redirects with ?error=unsupported_response_type appended to >> the end.
>> If I pass it response_type=code, then it returns the regular "Would >> you like to authorize this app to edit your Disqus forum" page, which >> isn't good.
>> Is there a response type that I should pass into the GET request that >> I don't know of?
>> Kevin
>> On Nov 19, 5:23 am, Michael HP <wus...@gmail.com> wrote: >> > i don't have documentation, but during bug testing i halted the >> > access_token request for at least 20 seconds before successfully >> > sending it, i'd imagine the code is valid for a little while longer >> > than that, but that really shouldn't be an issue.
>> > regarding question 3, you should read the documentation a bit >> > more(http://disqus.com/api/docs/auth/#response), the tokens are valid >> > for 30days, but you can make an automated process that use the refresh >> > token to request a new access_token without the user knowing.
>> > On Fri, Nov 18, 2011 at 8:25 PM, djangok <kevincheval...@gmail.com> >> wrote: >> > > I am able to retrieve the temporary code with /api/oauth/2.0/ >> > > authorize/
>> > > When I try to retrieve the Access Code from /api/oauth/2.0/ >> > > access_token/, I receive HTTP 400: Invalid API Version.
>> > > I've checked to make sure the format was correct. I tried it with >> > > curl on the command line, and with the python code supplied by Disqus. >> > > (https://github.com/disqus/disqus-api-demos/tree/master/comments) >> > > Both return the same response.
>> > > So, some questions: >> > > 1. How long does the temporary code last? 10 secs, 10 mins? Does it >> > > time out while I format the request by hand? (I'm just testing right >> > > now.) >> > > 2. Is there a problem with the server code at Disqus that is >> > > generating this request? >> > > 3. How long are the access tokens good for? I would really like to >> > > allow the Users to authorize my app forever. I can't make them >> > > authorize the app every time they log in.
> So, some questions: > 1. How long does the temporary code last? 10 secs, 10 mins? Does it > time out while I format the request by hand? (I'm just testing right > now.) > 2. Is there a problem with the server code at Disqus that is > generating this request? > 3. How long are the access tokens good for? I would really like to > allow the Users to authorize my app forever. I can't make them > authorize the app every time they log in.
> This produces the "Invalid API version" error. This error occurs whether I use the POST or GET methods.
> On Friday, November 18, 2011 12:25:31 PM UTC-7, djangok wrote:
> > I am able to retrieve the temporary code with /api/oauth/2.0/
> > authorize/
> > When I try to retrieve the Access Code from /api/oauth/2.0/
> > access_token/, I receive HTTP 400: Invalid API Version.
> > I've checked to make sure the format was correct. I tried it with
> > curl on the command line, and with the python code supplied by Disqus.
> > (https://github.com/disqus/disqus-api-demos/tree/master/comments)
> > Both return the same response.
> > So, some questions:
> > 1. How long does the temporary code last? 10 secs, 10 mins? Does it
> > time out while I format the request by hand? (I'm just testing right
> > now.)
> > 2. Is there a problem with the server code at Disqus that is
> > generating this request?
> > 3. How long are the access tokens good for? I would really like to
> > allow the Users to authorize my app forever. I can't make them
> > authorize the app every time they log in.
> > Kevin
> -- > --
> http://groups.google.com/group/disqus-dev?hl=en
So you'd have to have an account with password auth enabled to use it. Currently this requires you to submit an application describing your use case, and we review it and approve it on a case-by-case basis.
> So you'd have to have an account with password auth enabled to use it. > Currently this requires you to submit an application describing > your use case, and we review it and approve it on a case-by-case basis.
> -- > David Cramer
> twitter.com/zeeg
> disqus.com/zeeg
> On Tuesday, July 3, 2012 at 4:07 PM, Marcor wrote:
> So, some questions: > 1. How long does the temporary code last? 10 secs, 10 mins? Does it > time out while I format the request by hand? (I'm just testing right > now.) > 2. Is there a problem with the server code at Disqus that is > generating this request? > 3. How long are the access tokens good for? I would really like to > allow the Users to authorize my app forever. I can't make them > authorize the app every time they log in.
