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

# Modify A

> Modifies an existing A record on the domain's DNS zone.



## OpenAPI

````yaml PUT /api/v1/dns/a-record
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/a-record:
    put:
      tags:
        - DNS
      summary: Modify an A record
      description: Modifies an existing A record on the domain's DNS zone.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - order_id
                - current_value
                - new_value
              properties:
                order_id:
                  type: integer
                  description: Order ID of the domain.
                  example: 124680932
                current_value:
                  type: string
                  description: The existing IPv4 address of the record to modify.
                  example: 203.0.113.10
                new_value:
                  type: string
                  description: The replacement IPv4 address.
                  example: 203.0.113.20
                host:
                  type: string
                  description: >-
                    Subdomain label relative to the zone (e.g. `www`, `blog`).
                    Use `@` or omit for the apex domain.
                  example: www
                time_to_live:
                  type: integer
                  description: TTL in seconds. Minimum 300. Omit to use the zone default.
                  example: 300
            example:
              order_id: 124680932
              current_value: 203.0.113.10
              new_value: 203.0.113.20
              host: www
      responses:
        '200':
          description: A record modified successfully.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DnsRecordResponse'
              example:
                status: SUCCESS
                message: Record modified 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 this partner, or the upstream DNS
            provider rejected the request. The `message` field contains the
            reason — either `Invalid order ID` or a descriptive error from the
            DNS provider.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorInvalidOrder'
              examples:
                invalid_order:
                  summary: Unknown or unauthorised order ID
                  value:
                    status: ERROR
                    message: Invalid order ID
                upstream_rejection:
                  summary: DNS provider rejected the request
                  value:
                    status: ERROR
                    message: Failed to modify the record
components:
  schemas:
    DnsRecordResponse:
      type: object
      properties:
        status:
          type: string
          example: SUCCESS
        message:
          type: string
          example: Record added 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`.

````