> ## Documentation Index
> Fetch the complete documentation index at: https://docs.namify.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Activate DNS

> Activates the DNS service for a domain order, enabling DNS record management for that domain.

**Prerequisite:** DNS must be activated before any DNS records (A, AAAA, CNAME, MX, TXT) can be added to the domain. Call this endpoint once per domain before using the other DNS endpoints.

**Ownership check:** The `order_id` must belong to a domain under your partner account. Orders from other partners will be rejected with a 422.



## OpenAPI

````yaml POST /api/v1/dns/activate
openapi: 3.1.0
info:
  title: Namify API
  description: >-
    The Namify API gives resellers and platform builders programmatic access to
    domain search, registration, renewal, customer management, and DNS
    configuration — all through a single authenticated REST interface.


    All requests require a bearer token issued from the Namify dashboard
    (Settings > API Key). The API is scoped to your partner account: TLD
    availability, pricing, and order history are all filtered to your configured
    product catalogue.


    **Base URL:** `https://dev.namify.host`


    **Typical integration flow:**

    1. Create a customer account with `POST /api/v1/customers/signup`.

    2. Check domain availability with `GET /api/v1/domains/availability`.

    3. Register the domain with `POST /api/v1/domains/register`.

    4. Activate DNS with `POST /api/v1/dns/activate` and add records as needed.

    5. Renew the domain before expiry with `POST /api/v1/domains/renew`.
  version: 1.0.0
  license:
    name: MIT
servers:
  - url: https://dev.namify.host
security:
  - bearerAuth: []
paths:
  /api/v1/dns/activate:
    post:
      tags:
        - DNS
      summary: Activate DNS service
      description: >-
        Activates the DNS service for a domain order, enabling DNS record
        management for that domain.


        **Prerequisite:** DNS must be activated before any DNS records (A, AAAA,
        CNAME, MX, TXT) can be added to the domain. Call this endpoint once per
        domain before using the other DNS endpoints.


        **Ownership check:** The `order_id` must belong to a domain under your
        partner account. Orders from other partners will be rejected with a 422.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - order_id
              properties:
                order_id:
                  type: integer
                  description: >-
                    Order ID of the domain for which DNS service should be
                    activated.
                  example: 124680932
            example:
              order_id: 124680932
      responses:
        '200':
          description: DNS service activated successfully.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DnsActivateResponse'
              example:
                status: SUCCESS
                message: DNS service activated successfully
        '401':
          description: API key is missing or invalid.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorUnauthorized'
        '422':
          description: >-
            The `order_id` does not belong to a domain under your partner
            account.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorInvalidOrder'
              example:
                status: ERROR
                message: Invalid order ID
components:
  schemas:
    DnsActivateResponse:
      type: object
      properties:
        status:
          type: string
          example: SUCCESS
        message:
          type: string
          example: DNS service activated successfully
    ErrorUnauthorized:
      type: object
      required:
        - message
      properties:
        message:
          type: string
          example: Unauthorized
    ErrorInvalidOrder:
      type: object
      required:
        - status
        - message
      properties:
        status:
          type: string
          example: ERROR
        message:
          type: string
          example: Invalid order ID
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        A personal access token. Obtain one from the dashboard under Settings >
        API Key. Include it in the `Authorization` header as `Bearer <token>`.
        Unauthenticated requests to protected routes return `401 Unauthorized`.

````