Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shouldn't validate_token param be access-token, not auth_token? #270

Closed
wjdhamilton opened this issue Jun 14, 2015 · 1 comment · Fixed by #277
Closed

Shouldn't validate_token param be access-token, not auth_token? #270

wjdhamilton opened this issue Jun 14, 2015 · 1 comment · Fixed by #277

Comments

@wjdhamilton
Copy link

I note that in the doc entry for validate_token the params specified are auth_token and uid. When trying to use the endpoint in cURL I can only make it work with uid, access-token, and client. Shouldn't the docs reflect this or am I missing something?

@jasonswett
Copy link
Contributor

I believe access-token as opposed to auth_token is correct. That's what's working for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants