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

# Hello

> A lightweight health-check endpoint. Use this call to confirm that your bearer token is valid and that the API server is reachable. Returns the current server timestamp and a confirmation message. Ideal for testing credentials during initial integration or diagnosing authentication issues.



## OpenAPI

````yaml GET /api/v1/hello
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/hello:
    get:
      tags:
        - Authentication
      summary: Verify API connectivity and authentication
      description: >-
        A lightweight health-check endpoint. Use this call to confirm that your
        bearer token is valid and that the API server is reachable. Returns the
        current server timestamp and a confirmation message. Ideal for testing
        credentials during initial integration or diagnosing authentication
        issues.
      responses:
        '200':
          description: >-
            Authentication successful. Returns server time and a confirmation
            message.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HelloResponse'
              example:
                server_time: '2026-03-09 12:00:00'
                message: Authorized
        '401':
          description: The API key is missing or does not correspond to a known partner.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorUnauthorized'
components:
  schemas:
    HelloResponse:
      type: object
      properties:
        server_time:
          type: string
          description: Current date and time on the API server (YYYY-MM-DD HH:MM:SS).
          example: '2026-03-09 12:00:00'
        message:
          type: string
          description: >-
            Confirmation message indicating the request was authenticated
            successfully.
          example: Authorized
    ErrorUnauthorized:
      type: object
      required:
        - message
      properties:
        message:
          type: string
          example: Unauthorized
  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`.

````