# Register dynamic authentication

Create a new dynamic authentication registration for a device. Typically called during device onboarding or when associating a device with a stock for monitoring. Persists machine metadata, stock details, and contact number used for downstream verification and notifications.

Endpoint: POST /dynamic_auth/register
Version: 1.0.0
Security: ApiKeyAuth

## Request fields (application/json):

  - `machineId` (string, required)
    Unique identifier for the machine. Allowed characters: letters, numbers, dot, hyphen, underscore.
    Example: "MACHINE-001"

  - `stockName` (string, required)
    Name or code of the stock associated with the device (case-insensitive).
    Example: "ANDROID"

  - `totalPrice` (string, required)
    Total price string for the stock (supports comma-separated thousands and up to 2 decimals). Example formats: 200.00, 2,000.00.
    Example: "200.00"

  - `currentStockPrice` (string, required)
    Current market price as a string (same formatting rules as totalPrice).
    Example: "150.00"

  - `machineName` (string, required)
    Human-readable display name for the machine.
    Example: "Testing-2"

  - `mobile` (string, required)
    E.164 formatted mobile number for notifications and verification.
    Example: "+917837582588"

## Response 200 fields (application/json):

  - `status` (string, required)
    Indicates request success. Always success in this schema.
    Example: "success"

  - `message` (string, required)
    Short description of the successful operation outcome.
    Example: "Operation completed successfully"

## Response 400 fields (application/json):

  - `status` (string, required)
    Indicates failure. Always error in this schema.
    Example: "error"

  - `message` (string, required)
    Detailed explanation of the error to help clients fix the request.
    Example: "Invalid request parameters"


## Response 401 fields