ANNOUNCEMENT: Upcoming change to Yelp Fusion API Authentication – What to do?
This topic contains 8 replies, has 5 voices, and was last updated by Stiofan O’Connor 7 years, 9 months ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support TicketTagged: Yelp API Authentication
-
AuthorPosts
-
December 14, 2017 at 5:23 am #409484
Hi support team,
I got this info below from Yelp – What is in need to do to still use the yelp API for import listing details?
Best, Alex
Hello Yelp Developer!
As part of our efforts to make it easier to use the Yelp Fusion API, we are planning to deprecate the token endpoint (https://api.yelp.com/oauth2/token) on March 1, 2018. Instead of access tokens, we will use API Keys. For more details, please see our Authentication guide.Your access tokens have been automatically converted into API Keys that will never expire. If you had previously cached your access token, then no action is required and they will automatically keep working as API Keys. If you were not caching your access token, please see “Where is my client secret going?” for next steps. This change applies to both our Fusion and GraphQL APIs.
We want to give you plenty of time to remove all calls to the token endpoint so here is the timeline:
December 7, 2017 – Your API Key appears on the Manage App page. You should start using this API Key for calls to the Yelp Fusion API and GraphQL API. Just replace the access token in your code with your API Key.
March 1, 2018 – The token endpoint will be deprecated and you will need to remove all calls to the token endpoint. All calls to the Yelp Fusion API and GraphQL API should be authenticated with your API Key.Thanks,
Yelp TeamDecember 14, 2017 at 11:31 am #409523Yes it is likely we will have to make some changes again (they changes it not so long aog).
I have added a task for this and it will be in the next release.Thanks,
Stiofan
December 19, 2017 at 9:36 am #409999Hello Alex,
The changes for the upcoming yelp fusion api authentication has been implemented and will be in next release.
Kiran
January 11, 2018 at 2:25 pm #412322Hello, this Yelp API Section is making me really sick, can someone please Explain how/where to set the API Key and the Client Secret in the right fields inside Social Importer. None of Fields are having this names …
Just have this here:
App ID
App SecretConsumer Key
Consumer Secret
TokenSo – what is what?
Thanks in advance – and for serving me 🙂
Greetz from Austria – Joerg
January 12, 2018 at 4:52 am #412430Hello @wilderkaiser
The fusion api authentication changes will be available in next release of Social Importer.
If you have any issue with social importer, please open a new topic as you are not owner of this topic.Kiran
February 1, 2018 at 3:48 pm #415394Has this been updated in newest version? Will the Yelp stars replace the Multiratings and will the Yelp logo be applied to each listing that used this method to list?
February 1, 2018 at 7:14 pm #415436Hi Kent,
This has not been released yet, it will be released very soon.
It will not use the yelp stars or add a yelp logo.
You can replace the rating image yourself in the settings if you want to use a image similar to yelp.Thanks,
Stiofan
February 1, 2018 at 8:42 pm #415453I don’t want to use the Yelp stars but that’s one of their requirements. That, and the have each listing show the Yelp logo.
Since the update will not be within their rules, how can I delete the yelp reference from the social input field? Also, when I delete the Yelp codes from the social importer, and hit ‘Save Changes’, the codes are still there. How can I delete them?
February 2, 2018 at 12:32 pm #415615HI Kent,
The social importer is meant to allow users to pre populate their listing info from their facebook/yelp, the user has permission to use this info so there is no issue.
Thanks,
Stiofan
-
AuthorPosts
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket