# By Names and/or Position

You can get a tighter query than a full GeoJSON, faster and more tuned to your needs.

All of these requests are `GET` requests.

**You must always include a `maps` parameter in your request. You can send more than one at once to get results across multiple categories.**

For example:

```
https://native-land.ca/api/index.php?maps=languages,territories&position=42.553080,-86.473389&key=your_api_key
```

This request will get you all languages and territories that overlap with the \<lat>, \<lng> that you sent.

### By Position

To get by position, send a latitude and longitude as follows:

```
https://native-land.ca/api/index.php?maps=<category>&position=<lat>,<lng>&key=your_api_key
```

An example request might look like this:

```
https://native-land.ca/api/index.php?maps=languages&position=42.553080,-86.473389&key=your_api_key
```

### Specific Territories / Languages / Treaties

To get a specific nation, you need to know the identifying slug we use for that nation.

Look up the slug on Native-Land.ca, in the API section of your account after you log in. Just do a search for the nation you are interested in, and you will see all the available slugs you can use.

You can get more than one result at once, across multiple categories. Mix and match how you like!

An example query might look like this:

```
https://native-land.ca/api/index.php?maps=languages&name=nakota,lakota&key=your_api_key
```

You can also combine this with a position request, if you like.


---

# 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://api-docs.native-land.ca/by-names-and-or-position.md?ask=<question>
```

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.
