Fetch Guide

Guide to fetching information from Jena!

`GET` /ping

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

`GET` /uptime

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 :)

`GET` /info/commands

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!

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."}

PreviousAuthorization NextPost Guide

Last updated 2 years ago

Fetch Guide

`GET` /ping

CODE 200 (INT / MILLISECONDS)

CODE 203 (STRING)

`GET` /uptime

CODE 200 (INT / MILLISECONDS)

`GET` /info/commands

CODE 200 (OBJECT)

Code 400 (STRING)

hashtagGET /ping

hashtagCODE 200 (INT / MILLISECONDS)

hashtagCODE 203 (STRING)

hashtagGET /uptime

hashtagCODE 200 (INT / MILLISECONDS)

hashtagGET /info/commands

hashtagCODE 200 (OBJECT)

hashtagCode 400 (STRING)

`GET` /ping

CODE 200 (INT / MILLISECONDS)

CODE 203 (STRING)

`GET` /uptime

CODE 200 (INT / MILLISECONDS)

`GET` /info/commands

CODE 200 (OBJECT)

Code 400 (STRING)