Rest API: Authorization Endpoint

[Adi_Kurniawan]

Hello,

I'm trying to connect Marketo with other platforms using an integration tool. In order to authenticate with Marketo, it requires Client ID, Client Secret, Authorization Endpoint, and Token End point.

I can find all except Authorization Endpoint. Can anyone here help what should I do if the Authorization Endpoint is a required field?

Thanks,

Adi

[SanfordWhiteman]

There are not different "token" and "authorization" endpoints in the world of authorization. The /identity endpoint is for retrieving an access token. That's all you need.

Perhaps by "token" they mean the paging token endpoint, which we would not typically shorten to "token". Pretty bad UX if they're using that term.

[Floyd_Alvares2 · Accepted solution]

Hey @Adi_Kurniawan 

Do you have a screen shot of what the integration tool is requesting? Please ensure that no values are populated before posting.

Thanks

Floyd

[Adi_Kurniawan]

@Floyd_Alvares2  - It's an inhouse integration tool. Here's the screenshot:

Cheers,

Adi

[Floyd_Alvares2]

Taking a very wild guess here:

Authorization Endpoint - would this be the endpoint?

Token Endpoint - would this be the identity?

You can see the above information under Admin->Web Services.

If you hover on the more information - what does it specify?

[SanfordWhiteman]

If your in-house developers can't explain their own UI... that's not good.

As I mentioned, Marketo has one authorization endpoint, the /identity ep. There is no refresh token endpoint. The paging token endpoint is the only other value that possibly fits. But we don't call it a "token" endpoint - nor should the value need to be entered manually as it's derived from the Munchkin ID, just like /identity.