# LotaData API

> LotaData API on Apizie: 4 endpoints (Find event occurrences in the area. Returns results at specific place and time, event groups are expanded…, Get Specific event details., Venues, landmarks, regions, these are all places to search., Get specific place details) returned as clean JSON through one API key. Send your own provider key in the x-upstream-key header. Call it over REST at https://apizie.tech/v1/places:lotadata/{endpoint} or from Claude, ChatGPT and Cursor through the Apizie MCP server. Free plan: 1,000 requests a month.

- Project key: `places:lotadata`
- Category: Places
- Status: byok
- Source: https://lotadata.com
- Page: https://apizie.tech/api/places/lotadata
- OpenAPI: https://apizie.tech/api/places/lotadata/openapi.json

Access the most exhaustive, accurate and up-to-date collection of global and hyper-local geocoded events and activities across a wide range of categories and genres

## Endpoints

### Find event occurrences in the area. Returns results at specific place and time, event groups are expanded…
`GET https://apizie.tech/v1/places:lotadata/get-events` (byok)

| Parameter | Type | Required | Description |
|---|---|---|---|
| category | array | no | List of required EventCategory ids (Tier 1) |
| activity | string | no | List of required activity type ids (compliment to category) |
| ambience | string | no | List of required ambience ids |
| genre | string | no | List of required genre ids |
| name | string | no | Matching on event and place names |
| q | string | no | Text query matching titles, description, various text, tags, category |
| from_day | string | no | Start on or after date specified (2015-10-16) |
| to_day | string | no | Start on or before date specified (2015-10-16) |
| capacity_min | number | no | Min capacity at location |
| capacity_max | number | no | Min capacity at location |
| center | string | no | latitude,longitude of the origin point |
| radius | integer | no | Distance from origin in meters |
| bbox | array | no | Corner of a bounding box (lat,lng). Requires 0 or 2 pairs |
| polygon | array | no | Closed custom polygon. Ordered list of lat,lng pairs |
| within | string | no | Search within specified geopolitical place id |
| offset | integer | no | Return results starting at specified offset |
| limit | integer | no | Max results to return |
| fieldset | string | yes | Return results starting at specified offset (summary, context, detail) |

### Get Specific event details.
`GET https://apizie.tech/v1/places:lotadata/get-events-id` (byok)

| Parameter | Type | Required | Description |
|---|---|---|---|
| id | string | yes | event @id |
| fieldset | string | no |  |

### Venues, landmarks, regions, these are all places to search.
`GET https://apizie.tech/v1/places:lotadata/get-places` (byok)

| Parameter | Type | Required | Description |
|---|---|---|---|
| category | array | no | List of required PlaceCategory ids (Tier 1) |
| function | array | no | List of required PlaceFunction ids (Tier 2) |
| ambience | array | no | List of required ambience ids |
| tag | array | no | List of required tags |
| type | string | no | Specific PlaceType to return |
| name | string | no | Match on place names |
| exact | boolean | no | Require an exact name match |
| capacity_min | number | no | Min capacity at location |
| capacity_max | number | no | Min capacity at location |
| street | string | no | Address of the place or street component of the address |
| locality | string | no | city, town, or neighborhood of the place |
| region | string | no | region or state |
| postal_code | string | no | Postal or zip code |
| country | string | no | country component of the address |
| center | string | no | latitude,longitude of the origin point |
| radius | integer | no | Distance from origin in meters |
| bbox | array | no | Corner of a bounding box (lat,lng). Requires 0 or 2 pairs |
| polygon | array | no | Closed custom polygon. Ordered list of lat,lng pairs |
| within | string | no | Search within specified geopolitical place id |
| offset | integer | no | Return results starting at specified offset |
| limit | integer | no | Max results to return |
| fieldset | string | yes | Return results starting at specified offset (summary, context, detail) |

### Get specific place details
`GET https://apizie.tech/v1/places:lotadata/get-places-id` (byok)

| Parameter | Type | Required | Description |
|---|---|---|---|
| id | string | yes | place @id |
| fieldset | string | no |  |

## Example
```
curl "https://apizie.tech/v1/places:lotadata/get-events" \
  -H "x-api-key: $APIZIE_KEY" \
  -H "x-upstream-key: $PROVIDER_KEY"
```

## FAQ

### How do I call the LotaData API?
Create a free Apizie key, then send GET https://apizie.tech/v1/places:lotadata/get-events with the header x-api-key. Every endpoint returns { project, data, timestamp }.

### Is the LotaData API free on Apizie?
Yes. The Free plan includes 1,000 requests a month at 100 requests a minute, no credit card. LotaData itself also needs your own key from lotadata.com.

### Can AI agents use the LotaData API?
Yes. Add the Apizie MCP server (https://apizie.tech/mcp) to Claude, ChatGPT, Cursor or VS Code, then ask in plain language. The agent calls run_scraper with project key places:lotadata.

### What is the status of the LotaData API?
Needs your own provider key (bring your own key)