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

# Quickstart

> Generate your API token and make your first request

## API Token Generation

<Steps>
  <Step title="Access Server Settings">
    Navigate to your server's settings page in the Melonly dashboard.
  </Step>

  <Step title="Open Panel Section">
    Click on **"Panel"** in the server settings navigation.
  </Step>

  <Step title="Locate API Tokens">
    Scroll down to the **"Server API Tokens"** section.
  </Step>

  <Step title="Create New Token">
    * Click the token creation button
    * Enter a descriptive **name** for identification
    * Set an appropriate **expiry** date for your use case
    * Generate the token
  </Step>

  <Step title="Secure Your Token">
    <Warning>
      **Copy immediately:** The token is only displayed once and cannot be retrieved after this step.
    </Warning>

    Copy and store your API token in a secure location.
  </Step>
</Steps>

***

## Verify Integration

Test your newly created token with a server information request:

<CodeGroup>
  ```bash cURL theme={null}
  curl -H "Authorization: Bearer YOUR_API_TOKEN" \
    https://api.melonly.xyz/api/v1/server/info
  ```

  ```javascript JavaScript theme={null}
  const response = await fetch('https://api.melonly.xyz/api/v1/server/info', {
    headers: {
      'Authorization': 'Bearer YOUR_API_TOKEN'
    }
  });

  const data = await response.json();
  console.log(data);
  ```

  ```python Python theme={null}
  import requests

  headers = {
      'Authorization': 'Bearer YOUR_API_TOKEN'
  }

  response = requests.get('https://api.melonly.xyz/api/v1/server/info', headers=headers)
  data = response.json()
  print(data)
  ```
</CodeGroup>

### Expected Response

```json theme={null}
{
  "id": "server_12345",
  "name": "Your Server Name",
  "discordGuildId": "987654321098765432",
  "ownerId": "owner_67890",
  "createdAt": 1640995200,
  "joinCode": "ABC123"
}
```

***

## Security Considerations

<Accordion title="Token Management Best Practices">
  * **Rotation**: Implement regular token rotation schedules
  * **Scope**: Use separate tokens for different applications or environments
  * **Storage**: Never commit tokens to version control or expose in client-side code
  * **Monitoring**: Track token usage and implement alerting for unusual activity
</Accordion>

<Accordion title="Permission Model">
  API tokens inherit the permissions of the creating user. Ensure your account has the necessary server access levels for your intended API operations.
</Accordion>

***

## What's Next?

<CardGroup cols={2}>
  <Card title="Explore Endpoints" icon="route" href="/api-reference">
    Browse the complete API reference with detailed schemas and examples.
  </Card>

  <Card title="Implementation Examples" icon="code" href="/examples">
    View practical integration patterns and common use cases.
  </Card>
</CardGroup>

<Tip>
  Start with read-only endpoints like `/server/info` and `/server/members` to familiarize yourself with the API structure before implementing write operations.
</Tip>