JokeAPI Docs.txt

v2.3.2 (Changelog)
GitHub • Legal Stuff • Author
🔗Information:
JokeAPI is a REST API that serves uniformly and well formatted jokes.
It can be used without any API token, membership, registration or payment.
It supports a variety of filters that can be applied to get just the right jokes you need.
The usage is very simple and similar to other RESTful APIs and requires only basic knowledge of HTTP requests and JSON, XML, YAML or plain text.

If you come across a term you don't understand, you can try opening the menu and clicking on the section "Terminology".
JokeAPI currently serves 1368 jokes from 6 different languages. To submit a new joke, please click here.

To report a bug or a grammar mistake or to suggest a feature, please use the GitHub issue tracker.
If you want to contribute to JokeAPI, please read the Contributing Guide.

If you are new to JokeAPI, please start by reading the Getting Started Guide

§ Note:
If you enjoy using JokeAPI and want to support the development, please consider donating here ♥

I can't speak all languages, so please note that I can't ensure format and validity of jokes that aren't in English or German.
If you do come across an invalid joke or a joke that is formatted incorrectly, please consider opening an issue or submitting a pull request.

§ Uptime:
Last day:	
Last week:	
Last month:	
(more stats)

§ Security:
JokeAPI has been a target of DoS attacks in the past, which is why there is now a limit of 120 requests per minute and why joke submissions are manually curated. For more information click here.

All dependencies are tested for vulnerabilities by Snyk, you can find a summary of the known vulnerabilities here.
Page security score (powered by Mozilla Observatory): 
🔗News:
JokeAPI now has its own domain!
You can now replace the base URL https://sv443.net/jokeapi/v2 with https://v2.jokeapi.dev/
Note: you should always use the v2 subdomain to call the API but you can omit it if you just want to view the documentation.
For backwards compatibility the old URL will still be usable until version 2 will be deprecated.
Is JokeAPI serving too many offensive jokes?
Try using version 2.3.0's new safe mode and the explicit flag.
🔗Try it out here:
Select category / categories:	
Select language:	
Select flags to blacklist:	
Select response format:	
Select at least one joke type:	
Search for a joke that
contains this search string:	
Search for a joke
in this ID range:	
0
1367
Amount of jokes:	
1


URL: (Loading...)
Reset Form Send Request >
Result:

(Set parameters and click "Send Request" above)


🔗Getting Started:
JokeAPI doesn't require any API token, authorization or payment to work, although there is a hard limit of 120 requests per minute due to some DoS attacks I have been getting.
To start using JokeAPI, you can do one of these two things:
You can see if your language has a wrapper for JokeAPI (to see a list of officially supported wrappers, click here)
Then, follow its documentation to communicate with the API (Disclaimer: I don't take any responsibility for their code).
You can directly communicate with JokeAPI with HTTP requests (XHR) from within your code.
Here's a few resources to get you started: (Python XHR Crash Course, JavaScript XHR Documentation, .NET HttpClient Class Documentation)
Once you know how to send HTTP requests, please take a look at all the endpoints JokeAPI has.
After you've finished reading that, you can start testing out the different endpoints with a client such as Postman and look at some examples by going to the "Examples" section.


If your project really can't contain any explicit jokes, consider enabling the Safe Mode.

If you know any good jokes and want to add them to JokeAPI, please click here.
If you need any help, feel free to join my Discord server.

I struggled at explaining some features so consult the provided examples if you don't understand them.
🔗Official API Wrappers:
A wrapper library translates some API into an interface that is easier to use for a certain language or environment.
In the case of RESTful APIs like JokeAPI, a wrapper library makes it so you can use your language's features to communicate with the API while the wrapper will do all the HTTP requests for you in the background.

Disclaimer: I will not take any responsibility for the wrappers, they are community-made and I can't ensure security, validity and compatibility.
Also, some of these might be outdated or not finished yet. Please consider supporting the creators or contributing to the libraries :)

The following is a list of officially supported JokeAPI wrappers:

Language	Wrapper	Author
	Rust	Sv443_JokeAPI Rust Crate	canarado
	Python	Sv443s JokeAPI Python Wrapper	thenamesweretakenalready
	Node.js	JokeAPI - JavaScript wrapper	sahithyandev
	Dart	JokeAPI - Dart	MichaelDark
	Go	jokeapi-go	Icelain
	Java	Jokes4J	the-codeboy
	Java	JokeAPI - Java (com.simtechdata.jokeapi)	EasyG0ing1
	Java	JokeAPI - Java (uz.khurozov.jokeapi-java)	khurozov
  	Kotlin, Java, Android	JokeAPI for Kotlin, Java and Android	ethauvin
	C#	JokeAPI - C#	DanBuxton

(Click here to see the icon attributions)
🔗Submit a Joke:
Joke submissions have been disabled for the forseeable future.
Please see this GitHub issue for more info.
🔗Rate Limiting:
Due to JokeAPI being target of DoS attacks in the past, every client has a request budget of 120 requests they can send per minute.
Sending any requests after this limit will make the API temporarily give you a HTTP 429 error until the time runs out.
When submitting jokes, your budget is only 5 requests per minute.

Almost everywhere when using JokeAPI, you will be getting the following headers which tell you all you need to know about your current request budget:
Name	Description
Retry-After	Tells you in how many seconds your request budget gets reset back to 120
RateLimit-Limit	How many requests in total you can send to JokeAPI per minute
RateLimit-Remaining	How many requests you have left in your budget
RateLimit-Reset	Contains an IMF-fixdate timestamp of when your request budget gets reset back to 120
🔗URL Parameters:
URL parameters are like the settings or the configuration of an HTTP request.
The parameters need to be prefixed by a single question mark (?) and separate key/value pairs need to be delimited from another by an ampersand (&). Keys are separated from values with an equals sign (=).
Example: https://example.org/some/page?key1=foo&key2=bar&key3=baz ... (yellow = key/value pair)
§ Format:
?format=format

This parameter is global - it can be used on every single endpoint of JokeAPI (excluding the documentation and static content).
It is used to change the response format from the default (JSON) to (Loading...), depending on what you need.
If the format parameter is invalid or not specified at all, the default value of JSON will be used.
Available formats are (Loading...)

Example 1 (click to view)

Example 2 (click to view)


§ Blacklist Flags:
?blacklistFlags=flag1[,flag2,...]

This parameter can only be used on the "joke" endpoint.
If it is used, jokes that match the specified flag(s) will not be served (what is a flag?).
If you want to use multiple flags, separate them with a comma (,) or a plus sign (+).
These are all the available flags: (Loading...)

Example 1 (click to view)

Example 2 (click to view)


§ Language:
?lang=langcode

This parameter can be used on every endpoint, but it is possible that no translations or jokes exist yet for your language.

There are two types of languages; system languages and joke languages. Both are separate from each other.
All system messages like errors can have a certain system language, while jokes can only have a joke language.
It is possible, that system languages don't yet exist for your language while jokes already do.
If no suitable system language is found, JokeAPI will default to English.
The language codes in JokeAPI follow the ISO 639-1 / Alpha-2 specification.

If you are interested in providing translations, please read the Contributing Guide; it will explain it.
You can also submit jokes in different languages. Please understand that I will not be able to ensure their proper formatting or legitimacy.

Currently available system languages: (Loading...)
Currently available joke languages: (Loading...)

Example 1 (click to view)



§ Joke Type:
?type=type

This parameter can only be used on the "joke" endpoint.
If it is set, you will only receive jokes with the specified joke type (what is a joke type?).
If it is not set or set to an invalid value, you will receive jokes of both types.
Available types are: single, twopart

Example (click to view)


§ Contains:
?contains=string

This parameter can only be used on the "joke" endpoint.
If this parameter is specified, only jokes that contain the value of this parameter will be served (case insensitive).
IMPORTANT: If the value of this parameter contains special characters, it needs to be percent-encoded according to the URI syntax standard, otherwise you might get an error or a wrong response.

Example (click to view)


§ ID Range:
?idRange=number[-number]

This parameter can only be used on the "joke" endpoint.
If it is used, you will only get jokes that are inside the specified range of IDs.
The lower and upper boundary of the ID range needs to be delimited with a minus (-), comma (,) or a plus sign (+).
If you only want to get a single joke by its ID, you can also ignore the delimiter and just use the single ID as the value for this parameter.
As there are currently 1368 jokes, the ID range can be any range from 0 - 1367

Example 1 (click to view)

Example 2 (click to view)


§ Joke Amount:
?amount=number

This parameter can only be used on the "joke" endpoint.
If it is used, you will get a certain number of jokes in a single request.
If JokeAPI has less jokes than demanded, it will not error out but instead send the maximum amount of jokes it can serve.
Maximum possible number is 10 and using an invalid value will make JokeAPI default to 1.
The joke format will change from the default when you set the amount parameter to 2 or more.

Click to view the format when fetching multiple jokes

Example (click to view)



§ Submission Dry Run:
?dry-run

This parameter can only be used on the "submit" endpoint. It doesn't need a value (part to the right of the equals character).

If present, JokeAPI will respond just like the usual "submit" endpoint except the joke isn't actually saved to the API.
This functionality can be used to check if a joke is valid / what is wrong with it.

A successful dry run will have its error property set to false.
It will also have a message property with a short status message and a timestamp property with a 13-character UNIX timestamp.
🔗Safe Mode:
Safe Mode was added in version 2.3.0. If enabled, JokeAPI will try its best to serve only jokes that are considered safe for everyone.
Unsafe jokes are those who can be considered explicit in any way, either through the used language, its references or its blacklist flags.
Jokes from the category Dark are also generally marked as unsafe.

Note: this filter is really fine but that doesn't mean human error is out of the question.
If you find any jokes that you consider unsafe but are served even when safe mode is activated, please submit an issue here.

The Safe Mode can be enabled by adding the value-less URL parameter safe-mode to the URL.

Example 1 (click to view)

Example 2 (click to view)

🔗Errors:
In JokeAPI all response data, no matter from which endpoint will have a boolean "error" parameter.
Usually, it is set to false, which means there was no error in your request or on the server.
If the "error" parameter is set to true though, there was an error and JokeAPI will add an "internalError", "message", "causedBy", "additionalInfo" and "timestamp" parameter.

The "internalError" parameter will be set to false, if the error was due to a malformed or failed request and it will be true, if the error is JokeAPI's fault.
The "message" parameter will contain a short version of the error message and the "timestamp" parameter will contain a 13-character Unix timestamp.
The "causedBy" parameter is an array of possible causes of this error and the "addidionalInfo" parameter contains a more descriptive error message.

If possible, JokeAPI will try to translate the error messages but keep in mind there might not exist a translation for your language yet or it is not 100% perfect.
You can view an example of an error, where an invalid category was used, just below this paragraph.
Together with the HTTP status code, which will also be set according to the type of error, these parameters can be used to improve error handling massively from what was the error system in previous versions of JokeAPI.


Example Error:

    
{
    "error": true,
    "internalError": false,
    "code": 106,
    "message": "No matching joke found",
    "causedBy": [
        "No jokes were found that match your provided filter(s)"
    ],
    "additionalInfo": "The specified category is invalid - Got: \"foo\" - Possible categories are: \"Any, Misc, Programming, Dark, Pun, Spooky, Christmas\" (case insensitive)",
    "timestamp": 1579170794412
}

§ Status Codes:
Code	Name	Description
200	Ok	The request was accepted and processed successfully and the response text contains the requested data or a status message
201	Created	The joke submission is formatted correctly and was accepted and successfully saved (unless ?dry-run was used)
400	Bad Request	The request you have sent to JokeAPI is formatted incorrectly and cannot be processed
403	Forbidden	You have been added to the blacklist due to malicious behavior and are not allowed to send requests to JokeAPI anymore
404	Not Found	The URL you have requested couldn't be found
413	Payload Too Large	The payload data sent to the server exceeds the maximum size of 5120 bytes
414	URI Too Long	The URL exceeds the maximum length of 250 characters
429	Too Many Requests	You have exceeded the limit of 120 requests per minute and have to wait a bit until you are allowed to send requests again
500	Internal Server Error	There was a general internal error within JokeAPI. You can get more info from the properties in the response text
523	Origin Unreachable	My server is temporarily offline due to maintenance or an outage. Please be patient and check the status page.

Success • Client Error • Server Error
🔗Troubleshooting:
HTTP Error 403: First, please check if you can access all endpoints with your web browser. If not, your IP address has most likely been acting malicious and was permanently blacklisted.
If you keep getting HTTP 403 (Forbidden) response codes in your program but not in your browser and have never shown malicious behavior before, the issue is most likely that Cloudflare is blocking your request.
This might be due to inconsistent request data or headers that are often used in malicious requests or cyber attacks (most of the time it's gonna be the fault of the library you are using).
A fix to this issue would be to explicitly set a User-Agent header in each of your requests.
This is the user agent of your browser which you should be able to use in the fix described above:
(Something didn't work, please enter "navigator.userAgent" without quotes in your JavaScript console instead)

HTTP Error 429: You will get 429 errors occasionally if you exceed the maximum of 120 requests per minute.
In this case, you will need to wait up to one minute to be able to talk to the API again.
If you want to index the API or fetch all jokes, are better off going to the GitHub repository, where you will find everything you need and you don't need to spam JokeAPI.
🔗Endpoints:
An endpoint is an access point to send the HTTP requests to and get your response.
JokeAPI offers these following endpoints:

§ Get Joke:
 https://v2.jokeapi.dev/joke/[Category/-ies]

This endpoint is the one you want to call to get a joke.
A valid joke category or multiple joke categories, delimited with a comma, plus or minus character (, + -) must be provided in the URL.
These are all the available categories: (Loading...)
To see how this URL is built with certain parameters set, visit the "Try It" section.
Full example - click to view


Supported URL parameters:
?format
?blacklistFlags
?lang
?idRange
?contains
?type
?amount
(More info on filtering parameters)

§ Info:
 https://v2.jokeapi.dev/info

This endpoint provides a lot of information about JokeAPI and its jokes:
- The version number
- The amount of jokes
- All the available categories, flags, types and formats
- A 13-character UNIX timestamp
- The URL to a joke submission form
- A list of languages (code and name) JokeAPI currently supports
- The minimum and maximum values of an ID range per each language
- The amount of safe jokes there are per language
- A string with some information, like a message of the day

Supported URL parameters:
?format
?lang


§ Categories:
 https://v2.jokeapi.dev/categories

This endpoint returns a list / an array of all available joke categories, all available category aliases and a 13-character UNIX timestamp.

Supported URL parameters:
?format
?lang


§ Language Code:
 https://v2.jokeapi.dev/langcode/[Language]

This endpoint returns the ISO 639-1 language code of a provided language. It is searched with a fuzzy search, so you just have to provide the approximate language name.
The resulting language code is to be used in fetching and submitting jokes in different languages.

Example 1 - click to view

Example 2 - click to view


Supported URL parameters:
?format
?lang


§ Supported Languages:
 https://v2.jokeapi.dev/languages

This endpoint returns lists of supported languages in jokes and supported languages in system messages (error messages).
Also, it returns a list of possible ISO 639-1 language codes you can use to submit a joke or add a translation.
Example - click to view


Supported URL parameters:
?format
?lang


§ Flags:
 https://v2.jokeapi.dev/flags

This endpoint returns a list / an array of all available blacklist flags and a 13-character UNIX timestamp.

Supported URL parameters:
?format
?lang


§ Formats:
 https://v2.jokeapi.dev/formats

This endpoint returns a list / an array of all available response formats and a 13-character UNIX timestamp.

Supported URL parameters:
?format
?lang


§ Ping:
 https://v2.jokeapi.dev/ping

This endpoint returns a parameter named "ping" that contains the word "Pong!" and a 13-character UNIX timestamp.
It is intended for external uptime monitoring but you can also use it if you want to.

Supported URL parameters:
?format
?lang


§ Endpoints:
 https://v2.jokeapi.dev/endpoints

This endpoint returns a list / an array of all available endpoints, their usage (method, url and supported parameters) and a short description each.
Note: the lang parameter will not work here.

Supported URL parameters:
?format


§ Submit Joke:
 https://v2.jokeapi.dev/submit

This endpoint is used to programatically submit a joke to be reviewed and added to JokeAPI's official jokes.
If you instead just want to manually submit a joke, please click here.

To ensure backwards compatibility you can use the PUT method even though it is discouraged.
Using the PUT method might be deprecated in the future.

The payload needs to be sent as JSON. Different formats are not allowed here.
The request payload has to follow the same object structure that the jokes are served in when using the "joke" endpoint.

Make sure to add a "formatVersion" property, though, which just contains the current joke format version (3).
This is needed since there were a few changes to the object format since the previous versions and this serves as a kind of acknowledgement.

The joke category has to be any valid category, excluding "Any".
If the joke type is set to "single", the properties "setup" and "delivery" will need to be omitted and the joke is to be put in the "joke" property.
If the joke type is set to "twopart", the "joke" property is to be replaced with the properties "setup" and "delivery".
The "flags" property needs to be an object that contains the boolean properties "nsfw", "religious", "political", "racist", "sexist" and "explicit". These need to be set accordingly.
The joke ID doesn't need to be provided as it will be automatically assigned to the joke.

This endpoint has a unique URL parameter; ?dry-run, which if present will make the API respond just like the usual "submit" endpoint except the joke isn't actually saved to the API.
This functionality can be used to check if a joke is valid / what is wrong with it without having the joke actually submitted to the API.

If the joke is valid and the server accepted the submission, you will get a response with the status code 201.

Example Payload:

{
    "formatVersion": 3,
    "category": "Misc",
    "type": "single",
    "joke": "A horse walks into a bar...",
    "flags": {
        "nsfw": true,
        "religious": false,
        "political": true,
        "racist": false,
        "sexist": false,
        "explicit": false
    },
    "lang": "en"
}

Supported URL parameters:
?dry-run


Click here to see how the server responds to a joke submission


Click here to see how the server responds to a submission dry run



🔗Filtering Jokes:
I created JokeAPI with the main purpose of it having many versatile filtering options as other APIs didn't offer this amount of customization.
In this section you will learn how the filtering works.

There are six different filtering methods in JokeAPI:
Joke Category
Blacklist Flags
Response Format
Joke Type
Search String
ID Range
Language
🔗API Tokens:
JokeAPI has a way of whitelisting certain clients. This is achieved through an API token.
At the moment, you will only receive one of these tokens temporarily if something breaks or if you are a business and need more than 120 requests per minute.
If you do end up receiving a token, using it is as easy as adding an Authorization header with the actual token as its value.
You will receive a response header called Token-Valid which will contain the number 1 if the token is valid.
If the token is invalid, the Token-Valid header will be set to 0 and JokeAPI will treat your request as if you didn't supply a token in the first place.
🔗Examples:
These are some examples in some commonly used languages to show you how you could implement JokeAPI:

Node.js (click to show)

Web-JavaScript (click to show)

C# (click to show)

C# - Advanced (click to show)

🔗Terminology:
You might come across some terms in this documentation you don't understand. This section teaches you what those terms mean.
§ Categories:
JokeAPI has a first, coarse filter that just categorizes the jokes depending on what the joke is about or who the joke is directed at.
A joke about programming will be in the "Programming" category, dark humor will be in the "Dark" category and so on.
If you want jokes from all categories, you can instead use "Any", which will make JokeAPI randomly choose a category.
Since version 2.3.0, there are now aliases to these categories. This section explains how they work.

These are all the available categories: (Loading...)
To set the category you want, you need to add it to the URL path, just after the "/joke" endpoint, like this: https://v2.jokeapi.dev/joke/Programming
§ Category Aliases:
Since version 2.3.0, there are now category aliases. You can use these as a shorter or just different version of the normal set of categories.
Internally, these aliases will be resolved to one of the normal set of categories and your request (including the API's response) will be treated as if you used the resolved value.

The following is a list of aliases and what they will be resolved to internally:
Alias	Resolved Category

Example - click to view

§ (Blacklist-) Flags:
Blacklist Flags (or just "Flags") are a more fine layer of filtering.
Multiple flags can be set on each joke and they tell you something about the offensiveness of each joke.
You can tell JokeAPI to not give you jokes that have the specified flags by using the ?blacklistFlags URL parameter.

These are all the available flags: (Loading...)
§ (Response-) Formats:
Response Formats (or just "Formats") are a way to get your data in a different file format.
Maybe your environment or language doesn't support JSON natively. In that case, JokeAPI is able to convert the JSON-formatted joke to a different format for you.
You can tell JokeAPI which file format to respond with by using the ?format URL parameter.

These are all the available formats: (Loading...)
§ Joke Type:
Each joke comes with one of two types: single or twopart.
If a joke is of type "twopart", it has a setup string and a delivery string, which are both part of the joke.
They are separated because you might want to present the users the delivery after a timeout or in a different section of the UI.
A joke of type "single" only has a single string, which is the entire joke.
If you only want one type of joke, you can use the ?type URL parameter.

These are the available types: single, twopart
§ Search String:
If the search string filter is used, only jokes that contain the specified string will be returned.
You can specify this search string by using the ?contains URL parameter.
IMPORTANT: If the value of this parameter contains special characters, it needs to be percent-encoded according to the URI standard (MDN Reference), otherwise you might get an error or a wrong response.
§ ID Range:
If this filter is used, you will only get jokes that are within the provided range of IDs.
You don't necessarily need to provide an ID range though, a single ID will work just fine as well.
Example: an ID range of 0-9 will mean you will only get one of the first 10 jokes, while an ID range of 5 will mean you will only get the 6th joke.
You can set the ID range by using the ?idRange URL parameter.
As there are currently 1368 jokes, the ID range can be anywhere in the range of 0 to 1367
This range varies from language to language though, so I recommend taking a look at the /info endpoint, which contains all possible ID ranges.
§ Joke Amount:
This filter allows you to set a certain amount of jokes to receive in a single call to the "Get Joke" endpoint.
You can set it using the ?amount URL parameter.
Setting the filter to an invalid number will result in the API defaulting to serving a single joke.
Setting it to a number larger than 10 will make JokeAPI default to the maximum (10).
If you request more than 5 jokes, the API will try to serve them encoded with Brotli, Gzip or Deflate, depending on whether or not you set a Accept-Encoding header.
🔗Contributors:
The following is a list of people that have directly contributed to JokeAPI's development.
I am very grateful for this voluntary effort to improve JokeAPI and would like to thank anyone who contributed :)

(Loading...)


If you want to contribute to JokeAPI, please read this guide.
🔗Dependents:
These are some of the projects that depend on JokeAPI:
dozens Advices by ZephyrVentum
shadow-bot by QGIsK
Jokepy by aksty
Dark1 by whiteadi
Prejudice-Networks by LiamTownsley
https://irshad.ml/humour.html by draco-malfoy
Random-Joke-Generator-with-Flutter by variousnabil
comma by ThatCopy
Joke Teller by AlHood77
Jokes plugin for Craft CMS 3.x by remcoov
PoshBot.Joker by ToastIT-dev
JokeAPI_ComputerCraft by Sv443
Dev Dad Jokes by Jonathan Bossenger

(Submit an issue to get your project added here)
🔗Legal Stuff:
§ License:
JokeAPI is licensed under the MIT License.
Before modifying and / or redistributing the source code, please take two minutes to read the license text.
You can view the full license text by clicking here.

§ Privacy:
JokeAPI has to collect some anonymized data to work.
To view a list with details, please click here.
To view the privacy policy, please click here.
To view the site notice / imprint, click here.

§ Disclaimer:
I will hereby not claim any legal responsibility or liability for JokeAPI and the jokes it serves (especially those from the "Dark" category).
Whether it is used maliciously or breaks something in your project or someone gets offended by a joke, I can't be held accountable.
Additionally, I will only be able to provide security updates for a small selection of versions, a list of which you can find here.
I am doing my best to ensure security and stability but there's only so much a single developer can do.
Please report any issue that may arise to the GitHub issue tracker and I will try my best to fix it as soon as possible.
If you want to contact me, you can join my Discord server (fastest way to contact me) or send me an E-Mail: (click to show)
🔗Attributions:
These are the attributions to everything made by third parties that JokeAPI is based on or needs to function.

§ Fonts:
JokeAPI uses these third party fonts on its documentation page:
Cascadia Code by Microsoft
Roboto by Google


§ Other Attributions:
Third party icons used on this page:
The Rust icon is owned by Mozilla.
The Python icon is owned by the Python Software Foundation.
The Node.js icon is a trademark of the OpenJS Foundation.
The Go icon is owned by Google.
The Dart icon is owned by Google.
The C# icon is owned by Microsoft.
The Kotlin icon is owned by JetBrains.
The Java icon is owned by Oracle.
The Android icon is owned by Google.
The Sv443 Network is not endorsed by or affiliated with any of the above mentioned entities.
All of these icons are re-hosted for availability and to preserve the same format and are protected from being indexed by the majority of web crawlers.


The rectangular badges, like the ones found in the uptime and security sections, are powered by Shields.io

§ Libraries:
JokeAPI uses these libraries:
Code-Prettify by Google
JSLib by Sv443
These libraries are served using jsDelivr.


§ Dependencies:
These are the packages JokeAPI depends on (excluding dependencies of dependencies and devDependencies):
@pm2/io
dotenv
farmhash
fs-extra
fuse.js
http-ratelimit
js2xmlparser
json-to-pretty-yaml
mysql
node-wrap
promise-all-sequential
rate-limiter-flexible
request-ip
snyk
svjsl
url-parse
xss




© Copyright 2018-2021 Sv443 - licensed under the MIT license
This project is a part of the Sv443 Network