CPaaS Guide
API Guide
BlogLogin

IP Management API

Overview

The IP Management module allows parent account administrators to request, allocate, monitor, and configure dedicated IP addresses for their accounts and sub-acccounts.

Dedicated IPs improve email deliverability, give you control over sending reputation, and provide flexibility in managing your infrastructure.

👍

This is an add-on feature. Reach out to your Account Manager to enable this feature.

📘

Points to Remember

  • IP Management features are only available for parent accounts.
  • Sub-accounts cannot request or manage IPs directly.

Pre-Requisites

Before onboarding, ensure:

  1. Billing setup completed (dedicated IP feature is enabled only after billing is confirmed).
  2. Parent account permissions (sub-accounts cannot request or manage IPs).
  3. DNS access to configure and validate rDNS records.
  4. Volume forecast to determine the right number of IPs and warm-up plan.

Dedicated IP Lifecycle

1. Request IPs

Request Dedicated IPs

Request new dedicated IPs for your account based on sending volume and region requirements.

Key Rules

  • Only the parent account can request IPs.
  • The number of dedicated IPs for each account is limited. This limit is set during billing and feature enablement.
  • Supported regions: US, IND, EU.

Process

  1. Use your Request New dedicated IP API to request your IPs.
  2. Provide the following in the API request:
    • Number of IPs requested.
    • Daily Estimated Volume (emails/day).
    • Region (US/IND/EU).
    • Description (reason for request, max 250 characters, alphanumeric).
  3. Submit the request.
  4. Receive a Request ID for tracking in the API response.

What Happens Next

  • Allocation takes less than 1business days.
  • Requests may be Approved or Rejected.
  • If rejected, you’ll receive a reason (e.g., quota exceeded).
2. Check Request Status

Purpose: Track the status of your dedicated IP request. You can track your IP request using Get IP request status or Get all IP requests

Possible Status Values

  • Processing: Request is under review.
  • Approved: IPs are allocated and ready to configure.
  • Rejected: Request denied (e.g., quota or billing issue).

Details Provided

  • Number of IPs requested.
  • Number of IPs allocated. Depending on the use cases, you can receive more or fewer dedicated IPs than you requested. Note that you can always reach out to Netcore support in case of any discrepancy
  • Allocation details (IP addresses, region, warm-up status).
3. Configure Reverse DNS (rDNS)

Purpose

Authenticate your IPs by mapping them to your domain — essential for email deliverability.

Process

This critical phase requires action from both the user and our system.

  • Part A: Initiate Configuration & Update DNS
    1. Call the endpoint POST /v6/ip/request/rdns/configure .
    2. The customer must then take the sending_domain (received in the API response) and the associated ip_address
    3. Using the sending_domain map, the A record to your dedicated IP. (in your domain's DNS settings via your DNS provider e.g., GoDaddy, Cloudflare, AWS Route 53).
  • Part B: Validate the Configuration
    1. After the A record has been created and has had time to propagate, the customer must call POST /v6/ip/request/rdns/validate .
    2. System Action: Our system validates that the A record correctly points the subdomain to the IP. Simultaneously, our deliverability team is notified to update the corresponding PTR records for the dedicated IP.
    3. Then, we will update our PTR record to reflect the sending domain.

📘

We Recommend

rDNS must be configured for each dedicated IP, to maintain IP reputation.

4. Create and Manage IP Pools

Purpose: Organize IPs into groups for better control of different email streams. This is a best practice for separating email streams, such as "Marketing_Transactional" and "Corporate_Internal".

We highly recommend that you do this step to efficiently manage your entire IP pool.

Use this API to create IP pools. Once your IP pool is created, use Add IP to Pool API to add IPs and use Remove IP from Pool API to remove IP from the pool.

📘

Rules

  • Each pool can contain up to 100 IPs.
  • A parent account can create up to 100 pools.
  • Pool names must follow the format: ^[A-Za-z0-9_-]{3,50}$ and be unique.
  • Pools cannot mix IPs from different regions.
5: Assign IPs or Pools to Sub-Accounts

Purpose: Give sub-accounts(including parent account) access to dedicated IPs for their email sending.

📘

Important Points to Remember

  • Only parent accounts can assign/remove IPs or pools.
  • Assigning dedicated IPs will remove any shared IPs from the sub-account.
  • Ensure your IPs are warmed up before starting with your regular email volume. In case, you do not have a plan, you can always follow the warm up plan of Netcore.
  • Ensure you define(API request) not only the active domain but also the subdomain.

Options

  • Assign individual IPs: Select IPs and map them to sub-accounts/domains. To assign IPs directly to a subaccount: assign
  • Assign an IP Pool: Assign an entire pool for easier management. Use assign pools API to assign IPs to a pool.
  • To remove IPs, use the corresponding unassign or remove endpoints.

Validation Checks

  • IP must belong to the parent account.
  • Domain must be valid.
  • Cannot remove the last IP from a sub-account.

📘

Critical Migration Note

When dedicated IPs (or a pool) are assigned to a subaccount that is currently using shared IPs, the shared IPs will be removed automatically and replaced by the new dedicated IPs. Customers must perform this migration carefully and ensure their sending applications are prepared for the change to avoid any disruption to their email delivery.

📘

Best Practice

Plan migrations carefully — replacing shared IPs with dedicated IPs may affect email routing.

Best Practices

  • Keep IP pools region-specific (do not mix US, EU, IND IPs in one pool).
  • Separate marketing vs. transactional traffic across different pools.
  • Configure SPF, DKIM, and DMARC in addition to rDNS for complete domain authentication.
  • Plan migrations carefully: assigning dedicated IPs will remove shared IPs from sub-accounts.
  • Ensure your IPs are warmed up before starting with your regular email volume. In case, you do not have a plan, you can always follow the warm up plan of Netcore.