> For the complete documentation index, see [llms.txt](https://docs.predicthq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.predicthq.com/getting-started/guides/geolocation-guides/searching-by-location/find-events-by-iata-code.md).

# Find events by IATA code

For this example, we will use an IATA airport code to search for events around Los Angeles Airport on March the 3rd, 2018.

The `/events` API endpoint supports the use of IATA (three character), ICAO (four character), and UN/LOCODE (five character) airport codes. A CSV file with all supported airport codes and their respective place ids is available to download.

{% file src="/files/ZkhSwDSTdvJ5bh93C7jx" %}

We can use the IATA code for *Los Angeles Airport (LAX)*, `place.scope=LAX`, to find all the *concerts* events, `category=concerts`, which are active on *3rd of March, 2018*, `active.gte=2018-03-03` and `active.lte=2018-03-03`:

```python
import requests

response = requests.get(
    url="https://api.predicthq.com/v1/events/",
    headers={
      "Authorization": "Bearer $API_TOKEN",
      "Accept": "application/json"
    },
    params={
        "place.scope" : "LAX",
        "active.gte" : "2018-03-03",
        "active.lte" : "2018-03-03",
        "category" : "concerts",
        "sort" : "rank"
    }
)

print(response.json())
```

The following snippet shows the results:

```json
{
  "count": 73,
  "results": [
    {
      "id": "XS5tQbpjKtFeUShTPt",
      "title": "Demi Lovato with DJ Khaled and Kehlani",
      "category": "concerts",
      ...
    }
  ]
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.predicthq.com/getting-started/guides/geolocation-guides/searching-by-location/find-events-by-iata-code.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.