Trivia API

The Open Trivia Database provides a completely free JSON API for use in programming projects. Use of this API does not require a API Key, just generate the URL below use it in your own application to retrieve trivia questions.

All data provided by the API is available under the Creative Commons Attribution-ShareAlike 4.0 International License.

Getting Started

To get started using the Open Trivia DB API, use this URL: For more settings or help using the API, read along below. Alternatively, you can use the helper form to craft your specific query.

Session Tokens

Session Tokens are unique keys that will help keep track of the questions the API has already retrieved. By appending a Session Token to a API Call, the API will never give you the same question twice. Over the lifespan of a Session Token, there will eventually reach a point where you have exhausted all the possible questions in the database. At this point, the API will respond with the approperate "Response Code". From here, you can either "Reset" the Token, which will wipe all past memory, or you can ask for a new one.

Session Tokens will be deleted after 6 hours of inactivity.

Using a Session Token:

Retrieve a Session Token:

Reset a Session Token:

Response Codes

The API appends a "Response Code" to each API Call to help tell developers what the API is doing.

  • Code 0: Success Returned results successfully.
  • Code 1: No Results Could not return results. The API doesn't have enough questions for your query. (Ex. Asking for 50 Questions in a Category that only has 20.)
  • Code 2: Invalid Parameter Contains an invalid parameter. Arguements passed in aren't valid. (Ex. Amount = Five)
  • Code 3: Token Not Found Session Token does not exist.
  • Code 4: Token Empty Session Token has returned all possible questions for the specified query. Resetting the Token is necessary.
  • Code 5: Rate Limit Too many requests have occurred. Each IP can only access the API once every 5 seconds.

Encoding Types

The Open Trivia DB may contain questions which contain Unicode or Special Characters. For this reason, the API returns results in a encoded format. You can specify the desired encoding format using the examples below. If the encode type is not present in the URL, it will follow the default encoding.

API Call with Encode Type (urlLegacy, url3986, base64):

Example Sentence (Non Encoded): "Don't forget that π = 3.14 & doesn't equal 3."
  • Default Encoding (HTML Codes):
  • Legacy URL Encoding:
  • URL Encoding (RFC 3986):
  • Base64 Encoding:

Helper API Tools

There are some functions in the API which can be useful to developers.

Category Lookup: Returns the entire list of categories and ids in the database.

Category Question Count Lookup: Returns the number of questions in the database, in a specific category.

Global Question Count Lookup: Returns the number of ALL questions in the database. Total, Pending, Verified, and Rejected.

Limitations

  • Only 1 Category can be requested per API Call. To get questions from any category, don't specify a category.
  • A Maximum of 50 Questions can be retrieved per call.