---
title: "Assign IPs to subaccount"
method: POST
path: "/ip/assign"
tags: ["IP Management API"]
---

# Assign IPs to subaccount

`POST /ip/assign`

This allows a parent account to allocate one or more dedicated IP addresses to a subaccount by linking them with a specified sending domain. This ensures that the subaccount can send emails using the assigned IPs. The request must include the subaccount name, sending domain, and IP addresses, with all IPs belonging to the same region and owned by the parent account.

## Request body

- object
  - `assignments` object[], required — A list of assignment objects. Each obejct defines the mapping of one or more IP addresses to a specific subaccount and domain. You can send 1 to 10 assignments per request.
    - `ip_address` string[], required — The dedicated IP addresses to assign to the subaccount. Must be valid IPs owned by the parent account. Atleast one IP is required; up to 100 can be included per assignment. All IPs must belong to the same region.
    - `account_name` string, required — The Subaccount username that will receive the IPs. The subaccount must exit and belong to the authenticated parent account. Used to ensure the assignment is correctly linked.
    - `sending_domain` string, hostname, required — The domain that the subaccount will use with the assigned IPs. Must be an active, valid domain associated with the subaccount. Ensures email authentication and reputation are tied to the correct domain.
    - `region` 'US' | 'EU' | 'IND' — The geographic region of the IP addresses being assigned. Supported values are `US`, `EU`, `IND`. If provided, all IPs in the assignment must match the region.

## Response `200`

IPs assigned successfully

- object
  - `status` 'success' | 'partial_success' | 'error'
  - `message` string
  - `results` object[]
    - `account_name` string
    - `ip` string
    - `sending_domain` string
    - `status` 'success' | 'error'
    - `message` string

## Other responses

- `400` — Validation error
- `401` — Authentication required
- `403` — Access forbidden or ownership validation failed

---

[API](https://skmtc.dev/netcorecloud/apis/email-api-v6.md) · [All operations](https://skmtc.dev/netcorecloud/apis/email-api-v6/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/netcorecloud/email-api-v6/revisions/73f83bc2eff8/schema)