Responses

All of our API responses are structured in the same way, providing consistency across endpoints. The following fields are included:

number

An HTTP status code indicating the result of the request.

string

A brief, human-readable message indicating the result of the request.

object?

The requested information. This field is not always provided depending on the endpoint and request.

Example Response

{
  "code": 200,
  "message": "Bot statistics were fetched successfully.",
  "data": {
    "guilds": 10597,
    "users": 796787,
    "links": 38577
  }
}

Some more error responses can be found below as a reference.

400 Bad Request

{
  "code": 400,
  "message": "An invalid ID was provided."
}

401 Unauthorized

{
  "code": 401,
  "message": "Header 'Token' was not provided."
}

403 Forbidden

{
  "code": 403,
  "message": "You are blacklisted from Ducky."
}

405 Method Not Allowed

{
  "code": 405,
  "message": "Method POST is not supported on endpoint /statistics."
}

429 Too Many Requests

{
  "code": 429,
  "message": "Too many requests, please try again later."
}

For more information regarding ratelimiting, please refer to the Ratelimits page.

500 Internal Server Error

{
  "code": 500,
  "message": "An internal error occurred while processing this request. Please try again later."
}

Information

Internal Endpoints

Data Endpoints

Authentication Endpoints