# phpIPAM

> Connect a phpIPAM server to Cloud Management Platform (CMP) to manage addresses for your networks

---

Site [llms.txt](/llms.txt)

---

The setup workflow is common to all IPAM integrations: connect, import the networks, map them to your resource handler networks, and then enable orchestration. See [IP address management (IPAM)](/docs/cmp/configure/infrastructure/networks/ipam/) for those steps. This page covers what is specific to phpIPAM.

## Create an API key first

phpIPAM authenticates CMP with an application API key, so create one before you start. In phpIPAM, log in as an administrator and create an API key, setting the **App Security** to **SSL with User token**. You will enter that key's app ID in CMP.

## Connection details

In **Admin** > **IP Management**, select **Add**, then choose **phpIPAM**.

| Field | Description |
| --- | --- |
| **Name** | A name for this connection. |
| **IP address** | The address or hostname of the phpIPAM server. |
| **Protocol** | HTTP or HTTPS. Defaults to HTTPS. |
| **Account username** | An account authorized to run commands on the phpIPAM server. |
| **Password** | The password for that account. It is stored securely. If the password vault feature is enabled, this field offers **Locally Stored** or **Vault Managed**. Select **Vault Managed** to read the secret from a configured vault provider. See [Use password vaults](/docs/cmp/configure/access-and-security/security/use-password-vaults/). |
| **App id** | The app ID of the API key you created in phpIPAM. |

There is no **Port** field. phpIPAM does not use one, so CMP hides it, unlike the other three integrations.

## Related

- [IP address management (IPAM)](/docs/cmp/configure/infrastructure/networks/ipam/): The setup workflow shared by every IPAM integration.
- [Import and manage existing networks](/docs/cmp/configure/infrastructure/networks/import-existing/): The resource handler networks a phpIPAM network maps to.