Place ID

Important

Place IDs uniquely identify a place in the Geodir Places database and on Geodir.

Find the ID of a particular place.

A place ID is a textual identifier that uniquely identifies a place. The length of the identifier may vary. for example: XQgU3QsIFdpbG1pbmd0b24sDIDI4NDAxLCBVU0EiG, J0U6Ooscfq

Place IDs are available for most locations, including businesses, landmarks, parks, and intersections. It is possible for the same place or location to have multiple different place IDs. Place IDs may change over time.

You can use the same place ID across the Places API and a number of Geodir APIs. For example, you can use the same place ID to reference a place in the Places API, the Places API and more.

Save place IDs for later use

Place IDs are exempt from the caching restrictions stated of the Geodir Terms of Service. You can therefore store place ID values for later use.

You may occasionally receive a NOT_FOUND status code when you use a saved place ID. Best practice is to refresh your stored place IDs periodically. You can refresh Place IDs free of charge, by making a Place Fields request, specifying only the ID field in the fields parameter. This will trigger the Places Fields - 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.

A place ID may become obsolete if a business closes or moves to a new location.

Place IDs may change due to large-scale updates on the Geodir Maps database. In such cases, a place may receive a new place ID, and the old ID returns a NOT_FOUND response.

In particular, some types of place IDs may sometimes cause a NOT_FOUND response, or the API may return a different place ID in the response. These place ID types include:

• Street addresses that do not exist in Geodir as precise addresses, but are inferred from a range of addresses.
• Segments of a long route, where the request also specifies a city or locality.
• Crossing.
• Places with an address component of type subpremise.