Partners can match their unique property IDs to Tripadvisor property IDs. Once this has been done, the list of matched IDs can be stored in the Tripadvisor database. The list of partner-specific mappings can then be associated with the individual API key.
This call retrieves the full list of mappings currently stored in the Tripadvisor database for the partner. The response provides each unique partner_id and the corresponding tripadvisor_id. Number of items in a response is 1000 at maximum. An URL to brows the previous/next data will be provided in paging.
Access to this call is dependent on the existence of a stored mapping for the partner. Contact your Acccount Manager with any questions.
http://api.tripadvisor.com/api/partner/2.0/location_mappings/?key=PARTNER_KEY
| Name | Description |
| location_id | Optional: List of location_id's on which to report. |
| limit | Number of items returned. 1000 at maximum. |
| offset | Distance from the starting point of the list. |
{
"data": {
"locations": [
{
"partner_id": "a1005611",
"tripadvisor_id": "1005611"
},
{
"partner_id": "a103107",
"tripadvisor_id": "103107"
},
{
"partner_id": "a103109",
"tripadvisor_id": "103109"
}
],
"paging": {
"previous": null,
"skipped": "0",
"results": "3",
"next": "http://api.tripadvisor.com/api/partner/2.0/location_mappings?limit=3&offset=3&key=PARTNER_KEY",
"total_results": "2475"
}
}
}
| Name | Description |
| locations | An array of zero or more location objects, for the mapped properties for this IBE. |
| location.partner_id | The mapped Partner ID for one location. |
| location.tripadvisor_id | The Tripadvisor ID for the property -- for diagnostic purposes only. |
| paging | Information required to browse the next and previous sets of locations in the list, if they were not all returned as part of the current call. |