Skip to content
Free API Today

Open5e API

Open-licensed 5e monsters, spells and rules from several publishers.
Status
Working
API key
Not needed
Browser calls
Runs in the browser
Latency
170 ms
Docs
api.open5e.com ↗

Build snapshot, not live. One verifier run on , from the machine that built this site. How we check

Example request

GEThttps://api.open5e.com/v1/monsters/?limit=1

Sent from your browser straight to api.open5e.com. No proxy: this site never sees the request or the answer.

Copy the request

Shell
curl -s 'https://api.open5e.com/v1/monsters/?limit=1'

Response stored by the verifier

This is what api.open5e.com answered when the verifier sent the request above on : HTTP 200, application/json. Arrays are cut to two items and long strings are shortened. It comes from the build snapshot.

application/json · stored
{
  "count": 3207,
  "next": "https://api.open5e.com/v1/monsters/?limit=1&page=2",
  "previous": null,
  "results": [
    {
      "slug": "a-mi-kuk",
      "desc": "Crimson slime covers this ungainly creature. Its tiny black eyes sit in an abnormally large head, and dozens of sharp...",
      "name": "A-mi-kuk",
      "size": "Huge",
      "type": "Aberration",
      "subtype": "",
      "group": null,
      "alignment": "chaotic evil",
      "armor_class": 14,
      "armor_desc": "natural armor",
      "hit_points": 115,
      "hit_dice": "10d12+50",
      "speed": {
        "swim": 40,
        "burrow": 20,
        "walk": 30
      },
      "strength": 21
    }
  ]
}

Availability

Up 1 of 1 day checked · 30-day window

What counts as up for this API: an answer within five seconds, a 2xx status, and the JSON body must contain the field "results".

Last check: — passed, HTTP 200 in 170 ms.

The check runs from our infrastructure, not from where you are. If you need certainty, send the request yourself above. How the verifier works.

Questions

Does the Open5e API need an API key?

No. The sample request on this page was answered without a key, token or account.

Can I call the Open5e API from the browser?

Yes. api.open5e.com answered our verifier with an Access-Control-Allow-Origin header on Oct 3, 2026, so a fetch call from a web page can read the response.

Is the Open5e API working?

At the check on Oct 3, 2026 it returned HTTP 200 with the expected data in 170 ms. The status at the top of this page shows the most recent result we have.