---
title: "Add Custom Tracking Domain"
method: POST
path: "/v1/management/ctd/add"
tags: ["Custom Tracking Domains"]
---

# Add Custom Tracking Domain

`POST /v1/management/ctd/add`

## Request

- Base URL: `https://api.leadboxer.com`
- URL: `https://api.leadboxer.com/v1/management/ctd/add`
- Auth: API key in header `x-api-key`

Adds a custom tracking domain to the dataset and triggers the certificate generation process. <br/><br/><b>Note:</b> This operation may take several minutes to complete.<br/><br/>The response indicates whether the request resulted in an error, completed successfully, or requires additional DNS configuration.

## Request body

- CustomTrackingDomainRequest
  - `ctd` string, required
  - `datasetId` string, required
  - `description` string: Description for the given custom tracking domain

## Response `200`

Indicates the result of adding a custom tracking domain.<br/>Response code 0 indicates success, while response code -1 indicates failure; details are provided in the responseMessage.

## Other responses

- `400`: Bad Request: The request is invalid or malformed (missing/incorrect parameters).
- `402`: Payment Required: The client has exceeded credit limits.
- `403`: Forbidden: The authenticated user does not have permission to access this resource.
- `404`: Not Found: The requested resource does not exist.
- `409`: Conflict: The request could not be completed due to a resource state conflict.
- `429`: Too Many Requests: Rate limit exceeded. The client has sent too many requests in a given time period
- `500`: Interval Server Error: An unexpected error occurred on the server.

---

[API](https://skmtc.dev/leadboxer/apis/leadboxer-api.md) · [All operations](https://skmtc.dev/leadboxer/apis/leadboxer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/leadboxer/apis/leadboxer-api/revisions/34249b480395?raw)