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

# Melonly API

> Production REST API for ROBLOX server management automation

## Overview

The Melonly API provides programmatic access to Roblox server management infrastructure. Purpose-built for developers creating automated workflows and integration systems.

<Info>**Self-service documentation only** - No technical support provided</Info>

<Warning>
  Designed for experienced developers familiar with REST APIs, authentication workflows, and production system integration. Review all documentation thoroughly before implementation.
</Warning>

***

## Core Capabilities

<CardGroup cols={2}>
  <Card title="Server Management" icon="server">
    Access server configuration, roles, and administrative metadata
  </Card>

  <Card title="Application Processing" icon="clipboard-check">
    Retrieve applications, responses, and manage approval workflows
  </Card>

  <Card title="Member Operations" icon="users">
    Query member data, roles, and Discord account linkage
  </Card>

  <Card title="Audit & Logging" icon="shield-check">
    Comprehensive logging, moderation records, and system events
  </Card>

  <Card title="Operational Data" icon="calendar">
    LOA requests, shift tracking, and join request management
  </Card>

  <Card title="And Much More" icon="bolt">
    There are so many more endpoints to explore!
  </Card>
</CardGroup>

***

## Technical Foundation

<Tabs>
  <Tab title="Authentication">
    **Bearer Token Required**

    All endpoints require authentication via Authorization header:

    ```http theme={null}
    Authorization: Bearer {your_api_token}
    ```

    Tokens are scoped to individual servers and inherit creator permissions.
  </Tab>

  <Tab title="Data Format">
    **Standardized JSON Responses**

    * **Timestamps:** Unix epoch integers
    * **IDs:** Internal string identifiers (not Discord IDs)
    * **Pagination:** `page`/`limit` query parameters
    * **Errors:** Consistent HTTP status codes with JSON error objects
  </Tab>

  <Tab title="Rate Limits">
    **Production-Ready Throttling**

    * **Non-Premium:** 100 requests per month per server
    * **Premium:** Unlimited requests per month per token
    * **Headers:** `X-RateLimit-*` headers included in responses
    * **429 Status:** Returned when limits exceeded
  </Tab>
</Tabs>

***

## Implementation Workflow

<Steps>
  <Step title="Generate API Token">
    Create your server API token through the Melonly dashboard Panel settings.
  </Step>

  <Step title="Review Documentation">
    Study endpoint specifications, required parameters, and response schemas.
  </Step>

  <Step title="Implement Error Handling">
    Build robust error handling for all HTTP status codes and rate limits.
  </Step>

  <Step title="Test Integration">
    Validate your implementation against development endpoints before production.
  </Step>
</Steps>

***

## Quick Reference

<AccordionGroup>
  <Accordion title="Base URL & Versioning">
    **Production:** `https://api.melonly.xyz/api/v1`

    API versioning follows semantic versioning principles. Breaking changes will increment the major version number.
  </Accordion>

  <Accordion title="Common Status Codes">
    * `200` - Success with response body
    * `400` - Bad Request (invalid parameters)
    * `401` - Unauthorized (missing/invalid token)
    * `404` - Not Found (resource doesn't exist)
    * `429` - Rate Limited (too many requests)
    * `500` - Internal Server Error
  </Accordion>

  <Accordion title="Pagination Structure">
    ```json theme={null}
    {
      "data": [...],
      "page": 1,
      "pageSize": 10,
      "total": 150,
      "totalPages": 15
    }
    ```
  </Accordion>
</AccordionGroup>

***

## Get Started

<CardGroup cols={2}>
  <Card title="Quick Start Guide" icon="rocket" href="/quickstart">
    Generate your first API token and make a test request in minutes.
  </Card>

  <Card title="API Reference" icon="book-open" href="/api-reference">
    Complete endpoint documentation with schemas and examples.
  </Card>
</CardGroup>