canonical: https://jentic.com/apis/lotadata.com/lotadata-lotadata # LotaData LotaData is a hyper-local events and places data provider whose API exposes geocoded event occurrences and place records (venues, landmarks, regions) across global and local categories. The 4 endpoints cover event search, single event lookup, place search, and single place lookup - designed to enrich apps that need 'what is happening near here' or 'what venue is at this location' data. Authentication uses an api_key passed as a query parameter. ## For AI agents Search and enrich geocoded event and place data from LotaData - find events near coordinates, fetch event details, and resolve venue or landmark records - across 4 query-parameter API-key endpoints. ## Scope Does not handle ticket purchase, ride-hailing, or routing between places - use for LotaData event search and place lookup only. ## Capabilities - Search event occurrences within a geographic area filtered by category, genre, and time window - Retrieve a single event's full record including venue, time, and category metadata - Search for places - venues, landmarks, and regions - within or near a geographic area - Look up a single place's record including geocoded coordinates and category - Filter event and place search results by hyper-local categories rather than generic POI types ## Use cases ### Local discovery feature for travel apps Travel apps surface a 'happening near you' feed by querying LotaData's /events endpoint with the user's coordinates and a short time window. Because LotaData indexes hyper-local categories rather than only large ticketed events, the feed shows farmers' markets, neighbourhood concerts, and pop-ups that ticket-vendor APIs miss. The 4-endpoint surface fits in a single backend job. Example prompt: GET /events with bounding-box parameters around the user's location and a 7-day window, then fetch each high-priority event detail with GET `/events/{id}.` ### Location enrichment for ad targeting Ad-tech platforms use LotaData's place lookups to enrich impression coordinates with venue and category data - converting a raw lat/long into 'inside a stadium during a match' or 'near a farmers' market'. The /places search returns categorised records that feed audience segmentation rules without requiring a separate POI-and-events join. Example prompt: GET /places filtered to a 200m radius around the impression coordinate, then GET /events for the same area and current timestamp to detect any active venue activity. ### Smart-city dashboards Smart-city teams pull LotaData event and place feeds into operational dashboards to forecast crowd density, transit demand, and emergency-services load. Because the API exposes hyper-local categories, the dashboard can distinguish a small community event from a major stadium fixture - driving different staffing decisions for the same district. Example prompt: Schedule a job that queries GET /events for each city district every hour and writes the count and category breakdown to the dashboard's time-series store. ### Agent-driven local recommendations via Jentic An AI agent that helps users plan an evening calls LotaData through Jentic to find events and venues near a coordinate the user mentions in chat. The agent does not need to learn LotaData's specific category vocabulary - it asks Jentic for 'find events near a location' and gets back the right operation with its query parameters. Example prompt: Use Jentic to search 'find events near a location', load GET /events, execute it with the user's parsed coordinates and a tonight time window, and summarise the top results. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/events` | Search event occurrences in an area | | GET | `/events/{id}` | Get a specific event's details | | GET | `/places` | Search venues, landmarks, and regions | | GET | `/places/{id}` | Get a specific place's details | ## Key resources - **Events** — Search and retrieve geocoded event occurrences with category, genre, and time metadata - **Places** — Search and retrieve venues, landmarks, and regions as categorised geocoded records ## Why Jentic - **Setup:** Wiring LotaData by hand means passing your api_key as a query parameter on every request against api2.lotadata.com, and shaping event and place lookup parameters yourself. Through Jentic you install once, import LotaData from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** LotaData event and place lookups run against a shared directory rather than resources your account owns, so scoping is by operation: limit the agent to the operations it needs, such as searching events or fetching a single place, and leave out whichever lookup the agent does not use. - **Credential handling:** Your LotaData API key is stored once, encrypted, by your own Jentic One instance and appended as the query parameter at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'find events near a location' or 'look up a venue', and Jentic returns the matching LotaData operation with its query-parameter schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Ticketmaster Discovery API** — Major ticketed events search across venues, attractions, and classifications - **SeatGeek API** — Aggregated ticket marketplace with event and performer search - **Bandsintown API** — Concert and tour data centred on artists and their tour dates - **TomTom Maps API** — Map rendering and tile API for displaying LotaData events and places on a customer-facing map ## FAQ ### What authentication does the LotaData API use? LotaData uses an api_key sent as a query parameter (api_key=...). Through Jentic, the key is stored encrypted in the vault and Jentic appends it at execution time, so the raw key never appears in agent logs or chat context. ### Can I search for events near a specific coordinate with LotaData? Yes. GET /events accepts location and time-window parameters and returns matching event occurrences. Use Jentic search 'find events near a location' to load the operation and supply latitude, longitude, and the radius or bounding box. ### What are the rate limits for the LotaData API? LotaData enforces per-key request quotas tied to the subscription tier and returns HTTP 429 when exceeded. Jentic surfaces 429 responses unchanged so the agent can back off, and because the API has only 4 endpoints, quota tracking is straightforward to implement on the caller side. ### How do I look up a specific event's full record through Jentic? Search Jentic for 'get lotadata event details', load GET `/events/{id}`, and execute it with the event ID. The response includes venue (resolvable via GET `/places/{id}`), time window, and the LotaData category. ### Does the LotaData API include ticketing or pricing information? No - LotaData returns event metadata (location, time, category) and place records, not ticket inventory or prices. Pair it with a ticketing API such as Ticketmaster or SeatGeek when the workflow needs purchase data. ### How many endpoints does the LotaData API expose? Four: list events, get event by ID, list places, get place by ID. The whole surface area can be discovered in a single Jentic operation search. ### Can I limit what my agent is allowed to do with the LotaData API? Yes. Because you run Jentic One yourself, your own rules decide which LotaData operations and credentials the agent may use, and because LotaData reads a shared directory rather than resources your account owns, scoping is done per operation. You can grant only the calls the agent actually needs, such as searching events with GET /events or fetching a single place with GET `/places/{id}`, while withholding the event or place lookups it never uses. The stored API key is appended only when the agent invokes an operation you have allowed, so an agent limited to event search cannot reach place records or any other endpoint.