Error 601 from api -> reauthenticate -> error 601 again | Community
Skip to main content
A
Anonymous
October 16, 2017
Question

Error 601 from api -> reauthenticate -> error 601 again

  • October 16, 2017
  • 4 replies
  • 9415 views

I've been having an issue with some code we use, where I'm getting a 601 error response from the API, but when I re-authenticate, the next request also fails with a 601.

{"requestId":"5c99#15f16354ea4","success":false,"errors":[{"code":"601","message":"Access token invalid"}]}]

Re-authenticating should fix the problem according to here: http://developers.marketo.com/rest-api/error-codes/#response_level_error_codes

Has anyone run into this? Is this a bug on Marketo's side? Could it be caused by any setting in the Marketo account?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

4 replies

SanfordWhiteman
SanfordWhiteman
Level 10
October 16, 2017

Can you check your local system clock to make sure it hasn't slipped?

A
Anonymous
October 16, 2017

Requests made from the same machine around the same time work, it's only this one set of credentials that's exhibiting the issue.

A
Anonymous
October 16, 2017

I don't think that the expiration is the reason you're getting an error, as instead of 602 code you keep on getting 601. Try to enter in your browser xxx.mktorest.com/rest/v1/lead/1.json?access_token=yyy, where xxx is your rest endpoint id and yyy is your token. You should get 1004 error code (or the lead, if you have lead with id #1).

If you get 601 code — well, it basically means that your token is invalid.

A
Anonymous
October 16, 2017

I get {"requestId":"acfd#15f264682e9","success":false,"errors":[{"code":"601","message":"Access token invalid"}]}

This is the token give by marketo's api verbatim, so I'm not sure why it's invalid.

The documentation I linked above says:

An example of this is a 601, “Access token invalid,” which is recoverable by re-authenticating and passing the new access token with the request

A
Anonymous
October 16, 2017

You should read it this way: An example of this is a 601, “Access token invalid,” which is recoverable by re-authenticating and passing the new correct access token with the request

Get access token here: xxx.mktorest.com/identity/oauth/token?grant_type=client_credentials&client_id=yyy&client_secret=zzzz

xxx — client endpoint, yyy — client id, zzzz — client secret. Is the response ok? Does it have access_token and expires_in params? Do you treat it as json utf8 encoded response?

Nicholas_Manojl
Nicholas_Manojl
Level 8
October 16, 2017

On the other end, I'd double check there isn't a typo in the URL or the way the paramaters are included,

eg., ?access_token="xxxx"?fields=firstname

A
Anonymous
October 18, 2017

Creating a new API-Only User and a new LaunchPoint Service fixed the issue. I suspect that when the setup was done the first time, the user wasn't made an api-only user.

Terms & ConditionsAccessibility statement

Loading footer...