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

# Validate Custom Tracking Domain

`POST /v1/management/ctd/validate`

## Request

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

Validate the given custom tracking domain.

## Request body

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

## Response `200`

OK

- CustomTrackingDomainValidationResponse: Represents the response returned after validating a custom tracking domain. The response indicates whether validation failed, succeeded, or requires additional DNS configuration, and may include suggested CNAME records to complete setup.
  - `responseCode` integer
  - `responseMessage` string
  - `messageType` string: Indicates the result of custom tracking domain validation. - ERROR: Validation failed due to a client-side or server-side error. - WARNING: The domain is valid, but the DNS configuration is incomplete. Suggested CNAME records are returned. - SUCCESS: The domain is valid and correctly configured for tracking.
  - `suggestions` CTDSuggestionDTO[]: Recommended DNS record configurations needed to complete custom tracking domain setup.
    - `type` string: The DNS record type that should be configured for the custom tracking domain. This is typically a CNAME record required for tracking and link redirection.
    - `host` string: Tracking subdomain where the DNS record should be configured.
    - `value` string: Target hostname that the tracking subdomain must point to.

## 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)