# Locations, Destinations and Categories ### Overview Building great customer journeys starts with helping users find exactly what they’re looking for, quickly, intuitively, and with minimal friction. That’s why we provide a suite of powerful content discovery endpoints to help you deliver personalized and well-organized travel experiences across any platform. Whether you're creating a travel booking app, a city tourism portal, or a B2B reseller platform, our **Destinations**, **Locations**, and **Categories** APIs help structure and filter content so your users can explore effortlessly. *** ### Explore by Destination ```basic GET /products/destinations ``` #### What It Does Returns a list of destinations where your connected products are available. A *destination* typically refers to a high-level geographic area, a city, region, or tourist hub. #### Common Use Cases * A homepage travel search where users start by choosing a city like “Paris” or “Amsterdam”. * Building a landing page like `www.mytravelapp.com/rome/` that shows all activities in that city. * Displaying destination filters in a search form or sidebar. #### Real-World Scenario A reseller platform wants to offer "Travel by City" navigation. By calling this endpoint, the platform dynamically populates a list of available cities tied to products in their portfolio, without any hardcoding. Once a guest selects a city, they’re instantly shown relevant offers within that region. *** ### Zoom into Specific Places ```basic GET /products/locations ``` #### What It Does Returns a list of more granular *locations* where experiences take place. Think individual attractions, museums, venues, or parks. #### Common Use Cases * Displaying exact location info on product detail pages. * Enabling “near me” searches for mobile users using GPS-based filtering. * Showing products on a map view or geo-based clustering feature. #### Real-World Scenario Imagine a mobile travel app where a user enables geolocation. You can use `/locations` to fetch all venues within a certain radius of the user's current coordinates, allowing spontaneous bookings like “Skip-the-Line at the Van Gogh Museum – 100m away”. *** ### Group by Theme ```basic GET /products/categories ``` #### What It Does Returns a structured list of categories that group your product offerings into themes like “Museums”, “Boat Tours”, or “Day Trips”. #### Common Use Cases * Adding category filters to product listings or search UIs. * Organizing catalog pages, such as `/categories/tours`. * Letting users browse products by interest. #### Real-World Scenario Let’s say a user visits your app and filters by “Outdoor Activities”. Behind the scenes, you’re using the categories endpoint to populate these options dynamically, making your UI easier to maintain and future-proof as more experiences are added. *** ### Full Discovery Flow: From Idea to Booking Let’s say a user lands on your travel website looking for things to do in Barcelona. Here’s how you can help them: 1. **List Destinations**\ Fetch and display destinations so they can select "Barcelona". 2. **Filter by Location**\ After choosing Barcelona, show popular places, museums, parks, attractions, using `/products/locations`. 3. **Refine by Category**\ The user is interested in history and museums. Use `/products/categories` to let them drill down to relevant products like "Barcelona City History Tour" or "Skip-the-Line Sagrada Familia". *** ### Use in Dynamic UIs These endpoints are ideal for: * **Faceted search interfaces** (Destination + Category + Price Range) * **Autocomplete search suggestions** * **Map-based exploration** * **Custom itinerary builders** * **Localized or themed landing pages** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.prioticket.com/key-concepts/additional-capabilities/locations-destinations-and-categories.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.