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

Yelp Fusion switch to API KEYS #73

Closed
elope-developers opened this issue Jan 24, 2018 · 3 comments · Fixed by #74
Closed

Yelp Fusion switch to API KEYS #73

elope-developers opened this issue Jan 24, 2018 · 3 comments · Fixed by #74
Assignees

Comments

@elope-developers
Copy link

"Prior to December 7, 2017 the API used OAuth 2.0 to authenticate requests to the API. In an effort to simplify authentication, starting March 1, 2018 the API will no longer use OAuth 2.0 for requests and will move over to only API Keys. The token endpoint will be deprecated March 1, 2018, at which point you will no longer be able to make requests to it. "
-source: Yelp (https://www.yelp.com/developers/documentation/v3/authentication#where-is-my-client-secret-going)

Is there an update to support this in the roadmap? We're closing in on less than a month with no announced update for the yelp-ios project.

@SSheldon
Copy link
Member

I've put an update together in #74.

@SSheldon SSheldon self-assigned this Jan 29, 2018
@elope-developers
Copy link
Author

Thanks for the quick update and response! I can't wait to look into and apply the new commits!

@elope-developers
Copy link
Author

I'll leave this issue open until after the March switch happens so people get pointed to 74

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