Authvaultix
    Pages
    • Overview
    • Dashboard
    • Pages
    • API
    • Applications
    • Users
    • Subscriptions
    • Licence
    • Chatroom
    • Manage Accounts
    • seller keys
    • Seller Logs
    • Global Variables
    • User Variable
    • Sessions
    • Files
    • Blacklist
    • Whitelist
    • Webhooks
    • Logs
    • Audit Logs
    • Account
    • Settings
    • Forms
    • Upgrade
    • Bug Bounty
    Discord
    Github

    Seller Logs

    Seller Logs#

    The Seller Logs page is used to track all activity performed through the Seller API.
    It records which actions were called by bots or clients, which API queries were executed,
    which IP address made the request, and when the request occurred.
    This feature is mainly used for:
    • Security auditing (detect suspicious requests or unknown IP addresses)
    • Seller bot monitoring (verify Discord or Telegram bot activity)
    • Issue debugging (incorrect parameters or repeated API calls)
    • Abuse tracking (spam attempts, brute force, or invalid usage patterns)

    What does this feature do?#

    • Every Seller API request action is logged (example: create key, redeem, fetch, etc.)
    • The API query is stored (a short version is shown in the list)
    • The Seller Key is automatically masked for security reasons
    • The IP address is recorded for auditing and tracking
    • Date and time are displayed to show the activity timeline
    • Admins can delete individual logs or use Clear All to remove all logs
    • Pagination splits logs into pages (for example: 10 / 25 / 50 / 100 entries per page)

    Where can this feature be used?#

    1) Seller API Abuse Detection#

    • The same endpoint is repeatedly called
    • Requests are coming from unknown or foreign IP addresses
    • Unusual actions are being spammed
    Seller Logs allow you to quickly identify whether the API is being misused.

    2) Bot Integration Debugging#

    • The Discord or Telegram bot is not returning the expected response
    • Incorrect query parameters are being passed
    • The bot switched to the wrong application
    By reviewing the exact API query in the logs, the issue can be easily traced.

    3) Customer Support & Verification#

    • A user claims “the license was not created”
    • A seller claims “the API is down”
    Logs help verify whether the request was actually received and when it occurred.

    UI Flow#

    1) Page Header#

    • Title: Seller Logs
    • Subtitle: Monitor API activity and actions.
    Right-side buttons:
    • Clear All (only visible when logs exist)
    • Back to Keys (returns to the seller keys/configuration page)

    2) Controls / Filters#

    A search bar is available:
    • Placeholder: Search... (Client-side)
    • This search filters visible items on the current page in real time

    3) Desktop View (List/Table)#

    In desktop view, the table contains the following columns:
    • Action (badge indicator)
    • API Query (short form; full URL visible on hover/tooltip)
    • IP Address (may appear blurred or masked)
    • Date
    • Delete (remove a single log entry)
    Each log row includes:
    • An action badge indicating the request type
    • A summary of API parameters in the query column
    • An IP address for auditing
    • A timestamp showing when the action occurred

    4) Mobile View (Cards)#

    On mobile devices, logs are displayed as cards:
    • Top row: Action badge + Date
    • Middle: Short API query text
    • Bottom: IP address + Delete icon

    5) Masking / Security Note#

    Sensitive fields should be masked in logs. For example:
    • The sellerkey is hidden or replaced with ***
    This ensures that even if logs are shared, secret keys are not exposed.

    6) Pagination Footer#

    If many logs exist, pagination appears at the bottom:
    • Showing X to Y of Z entries
    • Prev / Next buttons
    • Page number range around the current page

    7) Client-Side Search Script#

    When typing in the search input, rows are filtered instantly:
    • Each row’s search text is converted to lowercase and compared
    • If a match is found → the row remains visible
    • If no match is found → the row is hidden
    The search typically works across a combination of Action + Query + IP.
    Modified at 2026-03-05 11:56:27
    Previous
    seller keys
    Next
    Global Variables
    Built with