Decovius API

A lightweight, Discord-powered hierarchical API system.
Access structured data using simple HTTP requests.

Access & Developer Requests

To request API access or developer usage, send an email to:

contact@developer.decovius.org

You may receive a response from:

info@email.decovius.org

⚠️ Do NOT send requests to info@email.decovius.org directly — they will not be processed.

How the API Works

Structure

The API uses a 3-layer system: 

Group → Sub → ID → Data

Backend Logic

Data is stored inside Discord channels:

  • Router channel → maps groups
  • Group channel → maps sub groups
  • Data channel → stores actual data

API Usage

Endpoint

https://api.decovius.org

Request

GET /?group=GROUP&sub=SUB&id=ID

With Password

GET /?group=GROUP&sub=SUB&id=ID&password=PASSWORD

Example

Request

https://api.decovius.org?group=users&sub=profile&id=user1

Response

{
  "success": true,
  "group": "users",
  "sub": "profile",
  "id": "user1",
  "data": "Example Data"
}

Password Protection

Passwords can be applied to:

If a password is set, the request must include: 

&password=YOUR_PASSWORD

Discord Data Structure

Router Channel

{"group":"users","channel":"123456789"}

Group Channel

{"sub":"profile","channel":"987654321"}

Data Channel

{"id":"user1","data":"John Doe"}

Error Responses

Missing Parameter

{
  "success": false,
  "error": {
    "code": "ERROR",
    "message": "Missing parameter"
  }
}

Not Found

{
  "success": false,
  "error": {
    "code": "NOT_FOUND",
    "message": "Data not found"
  }
}

Password Required

{
  "success": false,
  "error": {
    "code": "PASSWORD_REQUIRED",
    "message": "Password required"
  }
}

Important Rules

Performance Notes

The API uses caching to improve performance.
Changes in Discord may take a short time to update depending on cache duration.

Support

For questions or access requests:

contact@developer.decovius.org