Fetch Guide

Guide to fetching information from Jena!

GET /ping

ABOUT SECTION

This will return your connection latency to our API. This result is measured in milliseconds and is almost always in the double digits.

JSON OUTPUTS

CODE 200 (INT / MILLISECONDS)

{"status":"success","result":1}

CODE 203 (STRING)

{"status":"success","result":"Coming soon!"}

GET /uptime

ABOUT SECTION

Jena's uptime has been returned! This value is recorded in milliseconds and is mainly used for our dashboard, but there is no harm in making it public :)

JSON OUTPUTS

CODE 200 (INT / MILLISECONDS)

{"status":"success","result":1}

GET /info/commands

ABOUT SECTION

This is a treasure map for developers tinkering with Jena's features through our API, especially on Discord. It's like a behind-the-scenes peek that spills the beans on all the categories and specific commands Jena replies to. So, if you're the type looking to make Jena do your bidding, this is where you find all the secret handshakes to make the magic happen!

JSON OUTPUTS

CODE 200 (OBJECT)

{"status":"success","result": {
    categories: ["Category1", ...],
    commands: [
        {
            name: "command1",
            description: "It does stuff",
            category: "category1",
            options: [ "option1", ...]
        },
        // ...etc
    ]
})

Code 400 (STRING)

{"status":"fatal","error": "Jena has not been properly initialized, I have anonymously logged an error to our team."}