> ## Documentation Index
> Fetch the complete documentation index at: https://cerebrium-kyle-phase0-docs-fixes.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Cerebrium's documentation MCP server is available at https://cerebrium.ai/docs/mcp for searching and querying these docs directly. Install the Cerebrium agent skill with `npx skills add https://cerebrium.ai/docs`. Append .md to any docs page URL to fetch that page as plain Markdown. API keys and authentication tokens are created in the Cerebrium dashboard at https://dashboard.cerebrium.ai.

# Create Custom Domain

> Create a new custom domain for a project with DNS validation records.



## OpenAPI

````yaml https://s3.eu-west-1.amazonaws.com/www.cerebrium.ai/openapi_spec.json post /v2/projects/{project_id}/domains
openapi: 3.0.0
info:
  title: Cerebrium REST API
  description: >-
    REST API for interacting with Cerebrium. This API is mainly used by the
    Cerebrium CLI client, please run `pip install cerebrium` to install it.
  version: 1.0.0
  license:
    name: Proprietary
    url: https://www.cerebrium.ai/terms-of-service
servers:
  - url: https://rest.cerebrium.ai
security: []
paths:
  /v2/projects/{project_id}/domains:
    post:
      tags:
        - Custom Domains
      summary: Create Custom Domain
      description: Create a new custom domain for a project with DNS validation records.
      operationId: createDomain
      parameters:
        - name: project_id
          in: path
          required: true
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              properties:
                domain:
                  description: The domain name to add (e.g., api.example.com)
                  type: string
                domainType:
                  description: >-
                    Type of domain. Valid values: apex, subdomain. Wildcard
                    domains are not currently supported.
                  type: string
                region:
                  description: >-
                    The region the domain should route to (e.g., us-east-1).
                    Must match the region where the target app is deployed.
                  type: string
              required:
                - domain
                - domainType
                - region
              type: object
      responses:
        '201':
          description: >-
            The newly created custom domain, including the DNS record you must
            create to validate ownership.
          content:
            application/json:
              schema:
                properties:
                  createdAt:
                    description: Timestamp when the domain was created (RFC 3339).
                    type: string
                  dnsRecordName:
                    description: Name of the DNS record to create for validation.
                    type: string
                  dnsRecordType:
                    description: Type of DNS record to create for validation (e.g., CNAME).
                    type: string
                  dnsRecordValue:
                    description: Value of the DNS record to create for validation.
                    type: string
                  domain:
                    description: The custom domain name.
                    type: string
                  domainType:
                    description: Type of domain (apex or subdomain).
                    type: string
                  id:
                    description: Unique identifier of the custom domain.
                    type: string
                  projectId:
                    description: ID of the project the domain belongs to.
                    type: string
                  region:
                    description: The region the domain routes to.
                    type: string
                  updatedAt:
                    description: Timestamp when the domain was last updated (RFC 3339).
                    type: string
                  validationStatus:
                    description: Current DNS validation status of the domain.
                    type: string
                type: object
        '400':
          description: >-
            Bad request. The request was malformed or contained invalid
            parameters.
          content:
            application/json:
              schema:
                properties:
                  message:
                    description: Human-readable description of the error.
                    type: string
                type: object
        '401':
          description: >-
            Unauthorized. The Authorization header is missing or the token is
            invalid.
          content:
            application/json:
              schema:
                properties:
                  message:
                    description: Human-readable description of the error.
                    type: string
                type: object
      security:
        - BearerAuth: []
components:
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: >-
        Service Account Token authentication. To authenticate API requests:


        1. **Create a Service Account Token:**
           - Go to the [Cerebrium Dashboard](https://dashboard.cerebrium.ai/) and open the **API Keys** page
           - Click **Create Service Account**, name it (e.g., "GitHub Actions CI/CD"), choose an expiry date, and click **Create**
           - **Copy the token** generated for the desired service account

        2. **Use the Token:**
           Include the service account token in the Authorization header of API requests:
           `Authorization: Bearer <your-service-account-token>`

        3. **Best Practices:**
           - Create separate service accounts for different environments (dev, staging, prod)
           - Store tokens securely as secrets in consuming applications or workflows
           - Set appropriate expiry dates and rotate tokens regularly
           - Never commit tokens to source control

        For CI/CD integration examples, see the [CI/CD
        documentation](https://docs.cerebrium.ai/cerebrium/deployments/ci-cd).

````