> For the complete documentation index, see [llms.txt](https://help.aphex.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aphex.co/docs/integrations-and-api/external-map-layers/connect-nearmap-layers.md).
# Connect Nearmap Layers
{% hint style="info" %}
**Things to know before you get started:**
* This feature is available on Pro+ or Enterprise plans
* You need to be a Project Admin to set up the integration
* You’ll need an active Nearmap subscription with an API application set up. If the application you need isn’t listed when generating a key, contact your organisation’s Nearmap administrator.
{% endhint %}
If your team uses Nearmap for high-resolution aerial imagery, you can stream it directly into Aphex as a WMTS layer. This means your team plans against current, regularly-refreshed aerial imagery of the site, without downloading or re-uploading a thing.
This guide walks you through how to retrieve your API key from Nearmap, build your Layer URL, and add it to your project in Aphex.
### Retrieving your API Key
***
Nearmap authenticates WMTS requests using an API key tied to your user account, rather than a username and password.
**To retrieve your API key:**
* Log in to [MyAccount](https://apps.nearmap.com/account)
* Click `Integrations`, then the `API Keys` tab
* Choose the application you want to use from the dropdown
* Click `Create Key`
* Copy the key that appears in the API Key column - this is what you’ll use to build your Layer URL
### Constructing your Layer URL
***
Nearmap’s WMTS endpoint takes your API key as part of the URL path, rather than Aphex requesting it separately as a credential.
```
https://au0.nearmap.com/maps/api/wmts/v1/apikey/YOUR_API_KEY
```
Replace `YOUR_API_KEY` with the key you copied from MyAccount. This complete URL is what you’ll paste into Aphex - no additional parameters need to be added.
{% hint style="warning" %}
Use the subdomain for your region: `au0` for Australia/New Zealand, `us0` for US/Canada. Check with your Nearmap account if you’re unsure which applies to your subscription.
{% endhint %}
### Add the Layer to Your Aphex Map
***
Once you’ve got your Layer URL handy, you can plug it into any real-world Location in your Project.
Visit our Add Map Layers doc for step by step instructions on how to add layers to the Map.
### Set a Layer Policy
***
Nearmap maintains a history of aerial captures over time, so once connected, Aphex will detect each available capture date as a sublayer. A Layer Policy controls which of those are brought into your project, and how new captures are handled as Nearmap refreshes imagery for the site.
{% hint style="info" %}
Most Recent is usually the best starting point for Nearmap imagery, it keeps your map showing the latest capture without loading every historical survey.
{% endhint %}
Visit our Layer Policies doc for step by step instructions on how to define a layer policy.
---
# 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://help.aphex.co/docs/integrations-and-api/external-map-layers/connect-nearmap-layers.md?ask=&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.