I am setting up the plugin WP Google Review Slider, never thought it was so difficult!
I am getting error:
Deprecation notice: Obsolete Place IDs
and I cannot find where to refresh or update the place ID.
In WP dashword within the plugin I added the API key and I have to add as well the place id, when I do I gett this error message:
Google API Error: Wrong Key or Maps API not added. Due to recent changes by Google you must now add the Maps API to your existing API key in order to use the Location Lookup feature of the Google Places Widget.
View documentation here
and when I go to https://developers.google.com/maps/documentation/places/web-service/place-id, in order to get the place id I get this one: "Deprecation notice: Obsolete Place IDs" and there is no way who to find how to solve it.
Refresh the place id via:
GET https://maps.googleapis.com/maps/api/place/details/output?place_id=<your_place_id>?fields=place_id
From the docs:
We recommend refreshing place IDs if they are more than 12 months old. You can refresh Place IDs free of charge, by making a Place Details request, specifying only the place_id field in the fields parameter. This will trigger the Places Details - ID Refresh SKU. However, this request might also return NOT_FOUND status code. One strategy is to store the original request that returned each place ID. If a place ID becomes invalid, you can re-issue that request to get fresh results. These results may or may not include the original place. The request is chargeable.
Strategy
Call the Place details API to check if the place id is valid
https://maps.googleapis.com/maps/api/place/details/json?place_id=ChIJDx2VxLa1j4AR--kx601BUbY&fields=place_id&key=AIzaSyBiTgTvug0-W1RSaAZOT7cI4NgwzaRHVHc
(change "fields=place_id" to "field=" to see all fields)
It can result in following
Current google place id
Updated google place id
INVALID_REQUEST - (status code indicates that the specified place ID
is not valid)
NOT_FOUND - (status code indicates that the specified place ID is
obsolete. Id is obsolete if a business closes or moves to a new
location) (in this case lat long may not be useful if a business
moves to another location)
Handling the above conditions
Do not do anything (in the future may check also the last time data
is updated in DB to avoid frequent API calls)
Update the google place id inside DB and continue with the open map
Request the google details API with lat long to get a valid google
place id
Request the google details API with a place name to get a valid
google place id
Related
I am working on a pipeline which executes oAuth2 flow in order to access REST API json data. Once I have the bearer token I am executing a request which returns the following structure:
As you can see, since the response is quite large, there's paging enabled and as part of the response I get a link to the next page. In order to get to that resource I need to also present MS-ContinuationToken in the headers. So, this is how I basically do it in the config of the Copy activity that I use to get the data from the REST endpoint:
and the issue here is that I only get the first 2000 rows and the next page(s) don't seem to be visited at all. Pipeline executes successfully and only the first 2000 items are fetched.
NOTE: continuationToken and links.next.headers.value have the exact same values from the initial response.
Even if you fix the other issue you’ll have an issue with the “next” URL not including “v1”. This is a known issue in the partner center api team. I’ve escalated it pretty high. But they don’t want to break backwards compatibility by changing the “next” URI to include the v1 or to be relative. They are considering other options but I wouldn’t hold your breath.
I would ditch the idea of using data factory and instead write a .NET console app using the partner center SDK
(You might think to paginate manually with loops etc but the Copy activity doesn’t return eg the http headers, so you will need a complex set up to somehow store the data in a data store and be able to look up the last page in order to get the continuation token. I couldn’t figure it out)
I am trying to integrate Glympse into my application using their REST api. But I can not get user-shared location in a card from api /v2/tickets/{ticketID} with the ticketID I got from card member info. It always return invalid ticket ID.
I noticed there is a HTTPS push API. Is it true that user-shared location only can be got by HTTPS push API? Is it possible to get it by normal rest API?
It sounds like you know how to get to the invite code from a card, but I'll still include some of those steps in case it helps others.
This is how to get the user's list of cards.
Doc: https://developer.glympse.com/docs/core/api/reference/cards/get
Endpoint: https://api.glympse.com/v2/cards
This is how to get the details about a single card. You can also optionally pass "members=true" and/or "invites=true" to this call to get added details.
Doc: https://developer.glympse.com/docs/core/api/reference/cards/id/get
Endpoint: https://api.glympse.com/v2/cards/{cardId}?members=true
This is how to get a member of a card. The last ticket that was shared to the card will be found in the member's invite_code value.
Doc: https://developer.glympse.com/docs/core/api/reference/cards/id/members/mid/get
Endpoint: https://api.glympse.com/v2/cards/{cardId}/members/{memberId}
This is how to get the location data associated with a ticket invite code.
Endpoint: https://api.glympse.com/v2/invites/{inviteCode}?next={x}
The 'next' value is used to get just the location updates since the last call. When first querying an invite code, 'next' should be set to 0. For future calls on the same invite code, you should pass the 'next' value found in the previous call's result.
The location data is returned as a JSON array of delta values. More info on delta encoding here...
Doc: https://developer.glympse.com/docs/core/api/reference/tickets/id/append_location/post
when using github users api to return users data through
https://api.github.com/users?page=6&per_page=2
return the same data every one although change page parameter value and per_page
why this and how to fix to change different data
i try to edit header request and add this header
Name Link
Value <https://api.github.com/users?page=1&per_page=2>; rel="next",<https://api.github.com/users?page=50&per_page=2>; rel="last"
But Still not working
After my search
now Github use API V3 and if you want return users with paging you can use this
https://api.github.com/users?since=1&per_page=100
Instead of using "page" and "per_page", that endpoint uses "since" and "per_page".
The since parameter says from which user ID the API should start listing users. For example:
https://api.github.com/users?since=1&per_page=100
will start listing users from the user with ID 1, and
https://api.github.com/users?since=10001&per_page=100
will start listing users from the user with ID 10001.
I can see the my actual drop location on the receipts page on riders.uber.com, but do not see that data in requests/{request_id}/receipt/ end point of the API. Is there an alternative to get this data ?
I see that a GET on requests/{request_id}/ gives the actual location of the a ride, but does this point also gives the same data on ride completion/cancellation ? On sandbox-api, on completion of ride, I get location as null, on a GET requests/{request_id}/ call
The Uber API doesn't expose this information. It provides the destination of a trip in the request details, but it does not update the destination based on the actual drop-off location.
As pointed out in the comments, ONE partial alternative for this use case might be to use the request details array of waypoints. However, it is only available for shared rides like UberPOOL.
I have a development level access to Marketing API and it looks like I cannot read some fields of specific objects.
For example I try the following call:
You can see that promoted_object, link_url and object_url are not displayed in the result. And I should have one of those three value as the Ads was ad to promote "web site click".
Is it a bug or a limitation of the development acces or I am doing something wrong?
It is true that not all fields are readable by all apps, however in the case above it is most likely that these fields are empty on that object and therefore not returned in the response.
Promoted object, for example, is required on the adset level now, however it may be the case the adset you are trying to read is very old and therefore does not have one specified.
In regards to the creative fields, again not all creatives have these fields and in the case they are empty, are not returned in the response. You should check the promoted_story_id to see if this contains what you're looking for.