DropLoot.org API Reference

Messages Endpoints

The messages endpoints provide access to important platform-wide announcements, notifications, and update information. System messages are curated and intended to keep both users and integrators informed about significant changes, scheduled maintenance, or major releases.
All data is provided as structured JSON, suitable for programmatic consumption and front-end display.

• GET /api/messages/latest
  Retrieve the most recent, globally published announcement or informational message.
  This endpoint is ideal for applications that only need to display the latest platform-wide message without iterating through all historic notices.
  The response object contains unique identification, published date and time (in ISO 8601 UTC), message type, and the full message text.
  Example Response:

  {
    "id": 46,
    "text": "Maintenance scheduled for 2024-07-01 02:00 UTC.",
    "time": "2024-06-22T12:31:00Z",
    "type": "info"
  }

• GET /api/messages
  Returns a full list of all major system-wide messages and update notifications, sorted so the newest message appears first.
  Each object in the returned array includes the message's unique id, the full text, a time stamp (ISO 8601 UTC), and the type field (such as "info" or "update").
  Useful for audit, user interface presentation, or historical change tracking.
  Example Response:

  [
    {
      "id": 46,
      "text": "Maintenance scheduled for 2024-07-01 02:00 UTC.",
      "time": "2024-06-22T12:31:00Z",
      "type": "info"
    },
    {
      "id": 45,
      "text": "v2.1.0 is live — major updates deployed.",
      "time": "2024-06-14T06:02:27Z",
      "type": "update"
    }
  ]

Service Status and Information Endpoints

These endpoints enable clients to programmatically determine both the operational status and essential metadata of the DropLoot API service. They are suitable for API monitoring, uptime dashboards, health check integrations, or obtaining current service-level data.

• GET /api/ping
  Checks the health and responsiveness of the API server instance.
  Returns a pong value indicating an active connection, along with a responseTimeMs field showing the API's measured latency in milliseconds.
  Useful for both automated system health checks and for end users to confirm service availability.
  Example Response:

  {
    "pong": true,
    "responseTimeMs": 28
  }

• GET /api/info
  Returns a set of service metadata as a JSON object, including the service name, the current deployed API version, total platform uptime, and the current server time.
  The uptime value gives a human-readable duration since the last major restart or deployment.
  This endpoint is especially helpful for diagnostic, informational, or display purposes.
  Example Response:

  {
    "service": "DropLoot",
    "apiVersion": "2.1.0",
    "uptime": "6d 4h 21m",
    "time": "2024-06-22T18:02:02Z"
  }

Usage Notes and Integration Guidelines

• Content Type Specification: All API endpoints reliably respond with the application/json media type. Clients should ensure they send the Accept header set to application/json when making HTTP requests and parse responses accordingly.
• No Authentication Required: DropLoot public API endpoints are entirely open and require no authentication or API keys; this is for informational and monitoring access only, with no mutation or account-based operations.
• Public Data Safety: All returned message content is safe for users of all ages and may be displayed in user interfaces or relayed to client devices without additional moderation.
• Best Practices for Consumption: Please cache responses from endpoints such as /api/info and /api/messages when possible, in order to reduce unnecessary server load and improve response time for your users.
• Support and Contact: For questions, technical clarification, or to notify us about service issues, contact: admin@droploot.org. Our technical support team will be happy to assist with integration and troubleshooting guidance.
• Acceptable Use: The DropLoot API is designed and licensed for fair, good-faith use. Excessive, automated, or abusive access may be subject to rate-limiting or temporary restriction. Please see our Terms and Privacy Policy for more details.
• Data Retention and Change Frequency: Messages are retained in the system for at least 12 months and may be updated at any time to reflect new developments, planned downtime, or major feature releases.
• Uptime Monitoring: If you wish to monitor the DropLoot API's health from your own systems, the /api/ping and /api/info endpoints provide the essential data you need, updated in real-time.