> For the complete documentation index, see [llms.txt](https://docs.hamina.com/hamina/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hamina.com/hamina/live/extreme-networks.md).

# Extreme Networks

Learn how to Import/Export maps and AP locations from Hamina Network Planner to ExtremeCloud IQ and Extreme PlatformONE.

Hamina Network Planner features cloud-to-cloud integration with ExtremeCloud IQ and Extreme Platform ONE. The integration can be used in several ways:

* **Deploy a network** - Create a greenfield design in Hamina (including maps, scale, AP locations), and export it to Extreme for deployment. This eliminates any duplicate mapping work with Extreme.
* **Analyze an existing network** - Import a network from Extreme to Hamina, and see the current running configuration including the map, AP locations, channels, and transmit power. Add walls and attenuating objects to see how the current network looks inside a predictive model.
* **Modify an existing network** - Export the design from Hamina back to Extreme to implement any changes such as moving APs, adding APs, or changing AP models.

## Create an API Key

### Switching to Extreme Platform ONE

While it is likely possible to create an API key in ExtremeCloud IQ, we recommend switching to to Extreme Platform ONE for easy API key creation. To switch, click the 9-dot menu in the upper right, and select the **ExtremeCloud IQ (New)** link.

<div align="left"><figure><img src="https://1547340717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzUQ3TfKTYBeb6nf9W8Hv%2Fuploads%2FZlZX0nQKOtQuQPnocgl2%2Fswitch-to-ep1.png?alt=media&amp;token=3a3873db-b62a-4376-a0fd-291d2a2eabfe" alt="" width="375"><figcaption></figcaption></figure></div>

## Generating an API Token

1. Select the menu on the left-hand side.<br>

   <div align="left"><figure><img src="https://1547340717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzUQ3TfKTYBeb6nf9W8Hv%2Fuploads%2FjXQSgz25K3oUTLsE2F2L%2Fside-menu.png?alt=media&amp;token=a11cd346-4698-4bb0-a3a3-daf2cbbb2e1e" alt="" width="375"><figcaption></figcaption></figure></div>
2. Under **Administration & Settings**, select **Integrations**.<br>

   <div align="left"><figure><img src="https://1547340717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzUQ3TfKTYBeb6nf9W8Hv%2Fuploads%2Fr2wKVcJ2nbH1zq3NGxSC%2Fselect-integrations.png?alt=media&amp;token=2e8409a5-5292-40e3-9501-e895d45cffb3" alt="" width="375"><figcaption></figcaption></figure></div>
3. In the upper right, select **Create New API Key**.<br>

   <div align="left"><figure><img src="https://1547340717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzUQ3TfKTYBeb6nf9W8Hv%2Fuploads%2FU9ziEpH5kapFlUOaYw5A%2Fcreate-new-api-key.png?alt=media&amp;token=107e38e7-3cf7-4fff-9a27-3e7241562875" alt="" width="375"><figcaption></figcaption></figure></div>
4. In the **Create API Key** window, enter a name, description, and choose an expiration date. *<mark style="color:blue;background-color:blue;">Note: The name and description fields are required, but they don't need to be anything specific.</mark>*<br>

   <div align="left"><figure><img src="https://1547340717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzUQ3TfKTYBeb6nf9W8Hv%2Fuploads%2Fl9y4a79rVyIhLbpLbLe5%2Fcreate-api-key-modal.png?alt=media&amp;token=e8dd34e2-70d7-4280-920f-b9c52c594b12" alt="" width="563"><figcaption></figcaption></figure></div>
5. Copy the API key, and save it somewhere safe like a password manager. Then, select the **Close** button.<br>

   <div align="left"><figure><img src="https://1547340717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzUQ3TfKTYBeb6nf9W8Hv%2Fuploads%2FkREDaMuMPv2Av7d3KraR%2Fcopy-api-key.png?alt=media&amp;token=23329650-5dda-481a-9bc5-59c3d1d630b3" alt="" width="563"><figcaption></figcaption></figure></div>


---

# 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.hamina.com/hamina/live/extreme-networks.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.
