Authentication on developement freeagent


#1

Hi,

I go through with

http://dev.freeagent.com

first of all I created on app in my development account.

But pretty confuse about url and redirect url

I try to authenticate but from guide I am not able to clear that so.

Any real time example so I can easily go forward

Like url and authentication code and all access token.

I tried it for last 2 days but not able to get any output.

Please help me out on this.

Thanks,
Jimmy Darji


#2

​Sorry Martin, I realised I was getting muddled with the steps of the
process. I thought you were trying to request the authorization code in
Alteryx but reading back and looking at your other post I now see that
you’re generating that elsewhere and just trying to perform the token
exchange step here. Based on the screenshots you provided in your other
post you probably want to set it up as follows (though I’m not familiar
with Alteryx myself, so I’m just basing this on the screenshots here):

Headers:
Content-Type: application/x-www-form-urlencoded

Payload:
grant_type: “authorization_code”
code: this needs to be set from the authorization code you retrieved from
the first step. Either paste it in as a constant field or, select the field
it’s in if it’s stored somewhere else.
redirect_uri: This should be the URI you want to redirect the user back to
afterwards. You’ll need to URL encode this if Alteryx doesn’t do that for
you, but it most likely does so try just entering the URL as you would in
the browser first. If you enter this it must match the one you made with
the authorization request.

Connection:

Username: enter your client_id here
Password: enter your client_secret here

This should be everything you need to exchange the authorization token for
an access and refresh token. Good luck!

Regards,
Harry MillsOn Tue, Aug 30, 2016 at 2:17 PM, Harry Mills harry@freeagent.com wrote:

Hi Martin,

Sorry for the delay in getting back to you. When requesting an
authorization token you need to be adding the code, client_id and
client_secret to the request parameters, not to a header.

Content-Type shouldn’t matter for the authorisation token request as it’s
not using post data (it’s a GET request) but you’re using the right
Content-Type for the next step when you exchange the authorisation token
for an access token.


Regards,
Harry Mills

On Tue, Aug 23, 2016 at 3:58 AM, Martin Pohlers <martin.pohlers@ theinformationlab.de> wrote:

Hey Harry,

I generate the authorization code in the browser but without the
playground. It seems that I cannot use Alteryx for this step since it does
not open a browser to log into the account. I get the following error
message:

Sorry, there's been a problem.

To restart approval process please use your browser's back button to return to the app which sent you here.

For your second suggestion:
If I change the code, client_id and client_secret to the header the error
messsage changes to “invalid_request” from “invalid_grant”. The
Content-Type header is specified as

application/x-www-form-urlencoded

Do you have any more ideas?

Best Regards

Martin

On Monday, 22 August 2016 18:12:32 UTC+2, Harry wrote:

Hi Martin,

Sorry that you’re still having problems. How are you generating the
authorization code? Normally the OAuth flow is done all in one place, so
the same thing that requests the authorization code will then exchange it
for tokens. As authorization codes are only one use it’s fairly unusual to
pass them between systems. You also mention setting the body to
“code,client_id,client_secret”. This may be where you’re going wrong as
these should be passed as URL parameters, not in the body.

As an extra note, as well as the Accept header, you may wish to specify
the Content-Type header as well. This shouldn’t be affecting the token
exchange, as it doesn’t use the body, but for future requests this tells
the server that you’re sending data in JSON form.


Regards,
Harry Mills

On Mon, Aug 22, 2016 at 12:04 PM, Martin Pohlers < martin....@theinformationlab.de> wrote:

Hi Harry,

thank you for your reply!

I did consider this issue. I used an authorization code that I have not
used in the playground before. I used a separate one to see the call that
the playground makes and tried to adapt my workflow according to that and
your documentation.

I used https://api.sandbox.freeagent.com/v2/token_endpoint as the URL,
I have accept=application/json in the header and in the body
code,client_id,client_secret.

With grant_type=authorization_code I get the error message “invalid
grant” and with grant_type in the header I get “Invalid Request”.

I just created a new code which produced the exact same results.

What am I doing wrong?

On Monday, 22 August 2016 16:32:35 UTC+2, Harry wrote:

Hi Martin,

When you say you’re getting the tokens with the Google OAuth
Playground and then using the authorization code in Alteryx, do you mean
the same authorization code that the playground has already exchanged for
tokens? If so this won’t work as authorization codes are one use, so you
won’t be able to re-use it after the playground has exchanged it for
tokens. Depending on what you’re doing you might be able to give your
Alteryx integration the access and refresh tokens you’ve got from the
playground and let it refresh the access token as needed. Alternatively, if
you need to support multiple users then you’ll need to implement the OAuth
2.0 flow in Alteryx, requesting the authorization code from there and then
exchanging that for tokens as normal. Hopefully that helps.


Regards,
Harry Mills

On Fri, Aug 19, 2016 at 8:55 AM, Martin Pohlers < martin....@theinformationlab.de> wrote:

Hi,

I am having the same problems with OAuth 2.0.
I am using Alteryx the connect to the API but it does not work. I was
able to get the tokens with Google OAuth 2.0 Playground
https://code.google.com/oauthplayground/#step3&url=https%3A//&content_type=application/json&http_method=GET&useDefaultOauthCred=unchecked&oauthEndpointSelect=Custom&oauthAuthEndpointValue=https%3A//api.sandbox.freeagent.com/v2/approve_app&oauthTokenEndpointValue=https%3A//api.sandbox.freeagent.com/v2/token_endpoint&includeCredentials=unchecked.
Using this Authorization Code in Alteryx to get the tokens did not work. I
am stuck at the The Access Token Request step of the documentation.

Please help

Best Regards
Martin


You received this message because you are subscribed to the Google
Groups “FreeAgent API” group.
To unsubscribe from this group and stop receiving emails from it,
send an email to freeagent_ap...@googlegroups.com.
To post to this group, send email to freeag...@googlegroups.com.
Visit this group at https://groups.google.com/group/freeagent_api.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google
Groups “FreeAgent API” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to freeagent_ap...@googlegroups.com.
To post to this group, send email to freeag...@googlegroups.com.
Visit this group at https://groups.google.com/group/freeagent_api.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google Groups
“FreeAgent API” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to freeagent_api+unsubscribe@googlegroups.com.
To post to this group, send email to freeagent_api@googlegroups.com.
Visit this group at https://groups.google.com/group/freeagent_api.
For more options, visit https://groups.google.com/d/optout.


#3

Hi Harry,

thank you for your reply!

I did consider this issue. I used an authorization code that I have not
used in the playground before. I used a separate one to see the call that
the playground makes and tried to adapt my workflow according to that and
your documentation.

I used https://api.sandbox.freeagent.com/v2/token_endpoint as the URL, I
have accept=application/json in the header and in the body
code,client_id,client_secret.

With grant_type=authorization_code I get the error message “invalid grant”
and with grant_type in the header I get “Invalid Request”.

I just created a new code which produced the exact same results.

What am I doing wrong?On Monday, 22 August 2016 16:32:35 UTC+2, Harry wrote:

Hi Martin,

When you say you’re getting the tokens with the Google OAuth Playground
and then using the authorization code in Alteryx, do you mean the same
authorization code that the playground has already exchanged for tokens? If
so this won’t work as authorization codes are one use, so you won’t be able
to re-use it after the playground has exchanged it for tokens. Depending on
what you’re doing you might be able to give your Alteryx integration the
access and refresh tokens you’ve got from the playground and let it refresh
the access token as needed. Alternatively, if you need to support multiple
users then you’ll need to implement the OAuth 2.0 flow in Alteryx,
requesting the authorization code from there and then exchanging that for
tokens as normal. Hopefully that helps.


Regards,
Harry Mills

On Fri, Aug 19, 2016 at 8:55 AM, Martin Pohlers < martin....@theinformationlab.de <javascript:>> wrote:

Hi,

I am having the same problems with OAuth 2.0.
I am using Alteryx the connect to the API but it does not work. I was
able to get the tokens with Google OAuth 2.0 Playground
https://code.google.com/oauthplayground/#step3&url=https%3A//&content_type=application/json&http_method=GET&useDefaultOauthCred=unchecked&oauthEndpointSelect=Custom&oauthAuthEndpointValue=https%3A//api.sandbox.freeagent.com/v2/approve_app&oauthTokenEndpointValue=https%3A//api.sandbox.freeagent.com/v2/token_endpoint&includeCredentials=unchecked.
Using this Authorization Code in Alteryx to get the tokens did not work. I
am stuck at the The Access Token Request step of the documentation.

Please help

Best Regards
Martin


You received this message because you are subscribed to the Google Groups
“FreeAgent API” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to freeagent_ap...@googlegroups.com <javascript:>.
To post to this group, send email to freeag...@googlegroups.com
<javascript:>.
Visit this group at https://groups.google.com/group/freeagent_api.
For more options, visit https://groups.google.com/d/optout.


#4

Hi Martin,

Sorry for the delay in getting back to you. When requesting an
authorization token you need to be adding the code, client_id and
client_secret to the request parameters, not to a header.

Content-Type shouldn’t matter for the authorisation token request as it’s
not using post data (it’s a GET request) but you’re using the right
Content-Type for the next step when you exchange the authorisation token
for an access token.

Regards,
Harry MillsOn Tue, Aug 23, 2016 at 3:58 AM, Martin Pohlers < martin.pohlers@theinformationlab.de> wrote:

Hey Harry,

I generate the authorization code in the browser but without the
playground. It seems that I cannot use Alteryx for this step since it does
not open a browser to log into the account. I get the following error
message:

Sorry, there's been a problem.

To restart approval process please use your browser's back button to return to the app which sent you here.

For your second suggestion:
If I change the code, client_id and client_secret to the header the error
messsage changes to “invalid_request” from “invalid_grant”. The
Content-Type header is specified as

application/x-www-form-urlencoded

Do you have any more ideas?

Best Regards

Martin

On Monday, 22 August 2016 18:12:32 UTC+2, Harry wrote:

Hi Martin,

Sorry that you’re still having problems. How are you generating the
authorization code? Normally the OAuth flow is done all in one place, so
the same thing that requests the authorization code will then exchange it
for tokens. As authorization codes are only one use it’s fairly unusual to
pass them between systems. You also mention setting the body to
“code,client_id,client_secret”. This may be where you’re going wrong as
these should be passed as URL parameters, not in the body.

As an extra note, as well as the Accept header, you may wish to specify
the Content-Type header as well. This shouldn’t be affecting the token
exchange, as it doesn’t use the body, but for future requests this tells
the server that you’re sending data in JSON form.


Regards,
Harry Mills

On Mon, Aug 22, 2016 at 12:04 PM, Martin Pohlers < martin....@theinformationlab.de> wrote:

Hi Harry,

thank you for your reply!

I did consider this issue. I used an authorization code that I have not
used in the playground before. I used a separate one to see the call that
the playground makes and tried to adapt my workflow according to that and
your documentation.

I used https://api.sandbox.freeagent.com/v2/token_endpoint as the URL,
I have accept=application/json in the header and in the body
code,client_id,client_secret.

With grant_type=authorization_code I get the error message “invalid
grant” and with grant_type in the header I get “Invalid Request”.

I just created a new code which produced the exact same results.

What am I doing wrong?

On Monday, 22 August 2016 16:32:35 UTC+2, Harry wrote:

Hi Martin,

When you say you’re getting the tokens with the Google OAuth Playground
and then using the authorization code in Alteryx, do you mean the same
authorization code that the playground has already exchanged for tokens? If
so this won’t work as authorization codes are one use, so you won’t be able
to re-use it after the playground has exchanged it for tokens. Depending on
what you’re doing you might be able to give your Alteryx integration the
access and refresh tokens you’ve got from the playground and let it refresh
the access token as needed. Alternatively, if you need to support multiple
users then you’ll need to implement the OAuth 2.0 flow in Alteryx,
requesting the authorization code from there and then exchanging that for
tokens as normal. Hopefully that helps.


Regards,
Harry Mills

On Fri, Aug 19, 2016 at 8:55 AM, Martin Pohlers < martin....@theinformationlab.de> wrote:

Hi,

I am having the same problems with OAuth 2.0.
I am using Alteryx the connect to the API but it does not work. I was
able to get the tokens with Google OAuth 2.0 Playground
https://code.google.com/oauthplayground/#step3&url=https%3A//&content_type=application/json&http_method=GET&useDefaultOauthCred=unchecked&oauthEndpointSelect=Custom&oauthAuthEndpointValue=https%3A//api.sandbox.freeagent.com/v2/approve_app&oauthTokenEndpointValue=https%3A//api.sandbox.freeagent.com/v2/token_endpoint&includeCredentials=unchecked.
Using this Authorization Code in Alteryx to get the tokens did not work. I
am stuck at the The Access Token Request step of the documentation.

Please help

Best Regards
Martin


You received this message because you are subscribed to the Google
Groups “FreeAgent API” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to freeagent_ap...@googlegroups.com.
To post to this group, send email to freeag...@googlegroups.com.
Visit this group at https://groups.google.com/group/freeagent_api.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google
Groups “FreeAgent API” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to freeagent_ap...@googlegroups.com.
To post to this group, send email to freeag...@googlegroups.com.
Visit this group at https://groups.google.com/group/freeagent_api.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google Groups
“FreeAgent API” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to freeagent_api+unsubscribe@googlegroups.com.
To post to this group, send email to freeagent_api@googlegroups.com.
Visit this group at https://groups.google.com/group/freeagent_api.
For more options, visit https://groups.google.com/d/optout.


#5

Hi Jimmy,

When you set up your app the URL is just a reference for your users. For
example, you might set it to the homepage for your app.

The redirect URL is the page we’ll send users back to after completing the
authorization request. This will include the authorization code as a
parameter, so this is the page in your app that will get the authorization
code and exchange it for an access and refresh token, before showing the
user whatever you want them to see after successfully authenticating your
app with FreeAgent.

If you’re having trouble with the OAuth flow and want to ensure you’re
using the correct client ID and secret then we recommend trying it out on
the Google OAuth 2.0 Playground
https://code.google.com/oauthplayground/#step3&url=https%3A//&content_type=application/json&http_method=GET&useDefaultOauthCred=unchecked&oauthEndpointSelect=Custom&oauthAuthEndpointValue=https%3A//api.sandbox.freeagent.com/v2/approve_app&oauthTokenEndpointValue=https%3A//api.sandbox.freeagent.com/v2/token_endpoint&includeCredentials=unchecked
(the
link is for using with the FreeAgent API Sandbox, if you want to use it
with a production account you’ll need to change the URLs accordingly). The
instructions on the FreeAgent API documentation
https://dev.freeagent.com/docs/oauth should help with this. If you need
to enter a scope you can use whatever you like - the FreeAgent API doesn’t
use scopes but the playground requires them.

Hope this helps.

Regards,
Harry MillsOn Tue, Jul 26, 2016 at 1:23 AM, rkrlogical@gmail.com wrote:

Hi,

I go through with

http://dev.freeagent.com

first of all I created on app in my development account.

But pretty confuse about url and redirect url

I try to authenticate but from guide I am not able to clear that so.

Any real time example so I can easily go forward

Like url and authentication code and all access token.

I tried it for last 2 days but not able to get any output.

Please help me out on this.

Thanks,
Jimmy Darji


You received this message because you are subscribed to the Google Groups
“FreeAgent API” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to freeagent_api+unsubscribe@googlegroups.com.
To post to this group, send email to freeagent_api@googlegroups.com.
Visit this group at https://groups.google.com/group/freeagent_api.
For more options, visit https://groups.google.com/d/optout.


#6

Hi,

I am having the same problems with OAuth 2.0.
I am using Alteryx the connect to the API but it does not work. I was able
to get the tokens with Google OAuth 2.0 Playground
https://code.google.com/oauthplayground/#step3&url=https%3A//&content_type=application/json&http_method=GET&useDefaultOauthCred=unchecked&oauthEndpointSelect=Custom&oauthAuthEndpointValue=https%3A//api.sandbox.freeagent.com/v2/approve_app&oauthTokenEndpointValue=https%3A//api.sandbox.freeagent.com/v2/token_endpoint&includeCredentials=unchecked.
Using this Authorization Code in Alteryx to get the tokens did not work. I
am stuck at the The Access Token Request step of the documentation.

Please help

Best Regards
Martin


#7

Hey Harry,

I generate the authorization code in the browser but without the
playground. It seems that I cannot use Alteryx for this step since it does
not open a browser to log into the account. I get the following error
message:

Sorry, there's been a problem.

To restart approval process please use your browser's back button to return to the app which sent you here.

For your second suggestion:
If I change the code, client_id and client_secret to the header the error
messsage changes to “invalid_request” from “invalid_grant”. The
Content-Type header is specified as

application/x-www-form-urlencoded

Do you have any more ideas?

Best Regards

MartinOn Monday, 22 August 2016 18:12:32 UTC+2, Harry wrote:

Hi Martin,

Sorry that you’re still having problems. How are you generating the
authorization code? Normally the OAuth flow is done all in one place, so
the same thing that requests the authorization code will then exchange it
for tokens. As authorization codes are only one use it’s fairly unusual to
pass them between systems. You also mention setting the body to
“code,client_id,client_secret”. This may be where you’re going wrong as
these should be passed as URL parameters, not in the body.

As an extra note, as well as the Accept header, you may wish to specify
the Content-Type header as well. This shouldn’t be affecting the token
exchange, as it doesn’t use the body, but for future requests this tells
the server that you’re sending data in JSON form.


Regards,
Harry Mills

On Mon, Aug 22, 2016 at 12:04 PM, Martin Pohlers < martin....@theinformationlab.de <javascript:>> wrote:

Hi Harry,

thank you for your reply!

I did consider this issue. I used an authorization code that I have not
used in the playground before. I used a separate one to see the call that
the playground makes and tried to adapt my workflow according to that and
your documentation.

I used https://api.sandbox.freeagent.com/v2/token_endpoint as the URL, I
have accept=application/json in the header and in the body
code,client_id,client_secret.

With grant_type=authorization_code I get the error message “invalid
grant” and with grant_type in the header I get “Invalid Request”.

I just created a new code which produced the exact same results.

What am I doing wrong?

On Monday, 22 August 2016 16:32:35 UTC+2, Harry wrote:

Hi Martin,

When you say you’re getting the tokens with the Google OAuth Playground
and then using the authorization code in Alteryx, do you mean the same
authorization code that the playground has already exchanged for tokens? If
so this won’t work as authorization codes are one use, so you won’t be able
to re-use it after the playground has exchanged it for tokens. Depending on
what you’re doing you might be able to give your Alteryx integration the
access and refresh tokens you’ve got from the playground and let it refresh
the access token as needed. Alternatively, if you need to support multiple
users then you’ll need to implement the OAuth 2.0 flow in Alteryx,
requesting the authorization code from there and then exchanging that for
tokens as normal. Hopefully that helps.


Regards,
Harry Mills

On Fri, Aug 19, 2016 at 8:55 AM, Martin Pohlers < martin....@theinformationlab.de> wrote:

Hi,

I am having the same problems with OAuth 2.0.
I am using Alteryx the connect to the API but it does not work. I was
able to get the tokens with Google OAuth 2.0 Playground
https://code.google.com/oauthplayground/#step3&url=https%3A//&content_type=application/json&http_method=GET&useDefaultOauthCred=unchecked&oauthEndpointSelect=Custom&oauthAuthEndpointValue=https%3A//api.sandbox.freeagent.com/v2/approve_app&oauthTokenEndpointValue=https%3A//api.sandbox.freeagent.com/v2/token_endpoint&includeCredentials=unchecked.
Using this Authorization Code in Alteryx to get the tokens did not work. I
am stuck at the The Access Token Request step of the documentation.

Please help

Best Regards
Martin


You received this message because you are subscribed to the Google
Groups “FreeAgent API” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to freeagent_ap...@googlegroups.com.
To post to this group, send email to freeag...@googlegroups.com.
Visit this group at https://groups.google.com/group/freeagent_api.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google Groups
“FreeAgent API” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to freeagent_ap...@googlegroups.com <javascript:>.
To post to this group, send email to freeag...@googlegroups.com
<javascript:>.
Visit this group at https://groups.google.com/group/freeagent_api.
For more options, visit https://groups.google.com/d/optout.


#8

Hi Martin,

When you say you’re getting the tokens with the Google OAuth Playground and
then using the authorization code in Alteryx, do you mean the same
authorization code that the playground has already exchanged for tokens? If
so this won’t work as authorization codes are one use, so you won’t be able
to re-use it after the playground has exchanged it for tokens. Depending on
what you’re doing you might be able to give your Alteryx integration the
access and refresh tokens you’ve got from the playground and let it refresh
the access token as needed. Alternatively, if you need to support multiple
users then you’ll need to implement the OAuth 2.0 flow in Alteryx,
requesting the authorization code from there and then exchanging that for
tokens as normal. Hopefully that helps.

Regards,
Harry MillsOn Fri, Aug 19, 2016 at 8:55 AM, Martin Pohlers < martin.pohlers@theinformationlab.de> wrote:

Hi,

I am having the same problems with OAuth 2.0.
I am using Alteryx the connect to the API but it does not work. I was able
to get the tokens with Google OAuth 2.0 Playground
https://code.google.com/oauthplayground/#step3&url=https%3A//&content_type=application/json&http_method=GET&useDefaultOauthCred=unchecked&oauthEndpointSelect=Custom&oauthAuthEndpointValue=https%3A//api.sandbox.freeagent.com/v2/approve_app&oauthTokenEndpointValue=https%3A//api.sandbox.freeagent.com/v2/token_endpoint&includeCredentials=unchecked.
Using this Authorization Code in Alteryx to get the tokens did not work. I
am stuck at the The Access Token Request step of the documentation.

Please help

Best Regards
Martin


You received this message because you are subscribed to the Google Groups
“FreeAgent API” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to freeagent_api+unsubscribe@googlegroups.com.
To post to this group, send email to freeagent_api@googlegroups.com.
Visit this group at https://groups.google.com/group/freeagent_api.
For more options, visit https://groups.google.com/d/optout.


#9

Hi Martin,

Sorry that you’re still having problems. How are you generating the
authorization code? Normally the OAuth flow is done all in one place, so
the same thing that requests the authorization code will then exchange it
for tokens. As authorization codes are only one use it’s fairly unusual to
pass them between systems. You also mention setting the body to
“code,client_id,client_secret”. This may be where you’re going wrong as
these should be passed as URL parameters, not in the body.

As an extra note, as well as the Accept header, you may wish to specify the
Content-Type header as well. This shouldn’t be affecting the token
exchange, as it doesn’t use the body, but for future requests this tells
the server that you’re sending data in JSON form.

Regards,
Harry MillsOn Mon, Aug 22, 2016 at 12:04 PM, Martin Pohlers < martin.pohlers@theinformationlab.de> wrote:

Hi Harry,

thank you for your reply!

I did consider this issue. I used an authorization code that I have not
used in the playground before. I used a separate one to see the call that
the playground makes and tried to adapt my workflow according to that and
your documentation.

I used https://api.sandbox.freeagent.com/v2/token_endpoint as the URL, I
have accept=application/json in the header and in the body
code,client_id,client_secret.

With grant_type=authorization_code I get the error message “invalid grant”
and with grant_type in the header I get “Invalid Request”.

I just created a new code which produced the exact same results.

What am I doing wrong?

On Monday, 22 August 2016 16:32:35 UTC+2, Harry wrote:

Hi Martin,

When you say you’re getting the tokens with the Google OAuth Playground
and then using the authorization code in Alteryx, do you mean the same
authorization code that the playground has already exchanged for tokens? If
so this won’t work as authorization codes are one use, so you won’t be able
to re-use it after the playground has exchanged it for tokens. Depending on
what you’re doing you might be able to give your Alteryx integration the
access and refresh tokens you’ve got from the playground and let it refresh
the access token as needed. Alternatively, if you need to support multiple
users then you’ll need to implement the OAuth 2.0 flow in Alteryx,
requesting the authorization code from there and then exchanging that for
tokens as normal. Hopefully that helps.


Regards,
Harry Mills

On Fri, Aug 19, 2016 at 8:55 AM, Martin Pohlers < martin....@theinformationlab.de> wrote:

Hi,

I am having the same problems with OAuth 2.0.
I am using Alteryx the connect to the API but it does not work. I was
able to get the tokens with Google OAuth 2.0 Playground
https://code.google.com/oauthplayground/#step3&url=https%3A//&content_type=application/json&http_method=GET&useDefaultOauthCred=unchecked&oauthEndpointSelect=Custom&oauthAuthEndpointValue=https%3A//api.sandbox.freeagent.com/v2/approve_app&oauthTokenEndpointValue=https%3A//api.sandbox.freeagent.com/v2/token_endpoint&includeCredentials=unchecked.
Using this Authorization Code in Alteryx to get the tokens did not work. I
am stuck at the The Access Token Request step of the documentation.

Please help

Best Regards
Martin


You received this message because you are subscribed to the Google
Groups “FreeAgent API” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to freeagent_ap...@googlegroups.com.
To post to this group, send email to freeag...@googlegroups.com.
Visit this group at https://groups.google.com/group/freeagent_api.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google Groups
“FreeAgent API” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to freeagent_api+unsubscribe@googlegroups.com.
To post to this group, send email to freeagent_api@googlegroups.com.
Visit this group at https://groups.google.com/group/freeagent_api.
For more options, visit https://groups.google.com/d/optout.