List bosses

Huntera's boss doors as the game publishes them — 3 on the capture being served,
each keyed on the id the game files it under.

A row here is the door rather than the creature behind it. door carries what
it asks before it opens: a character level, a kill count, the creatures the count
is of, and the kin name the game uses when it states the requirement.

door.kills.each is the field to read before the count. It is true on one of the
three doors, where the 2,500 kills are required of each of the four creatures
rather than across them — so a client that ignores it reports that door's
requirement at a quarter of what the game asks.

entry and carried_in are the two lines the game shows on the way in, and they
are published exactly as it writes them. entry contains a literal {boss}
placeholder for a client to substitute the boss's name into; carried_in
contains none. Nothing here interpolates either.

mirrors is a mechanic one of the three bosses has, and it is null on the
other two rather than an object of empty numbers: those two do not have mirrors.

Nothing here is borrowed from tibia.dev, so fallbacks is empty on every row,
and there is no tibia object at all: Tibia has bosses but no boss doors to
mirror.

door.kills.monsters is door.kills.creatures now, which is a breaking change on
this endpoint.
Nothing else moved: the same list in the same order, and every
field inside it — creature_key, creature — spelled as it was. The word monster
survives where the capture wrote it, on huntera_boss_door_monsters and on the
relation that reads it, and nowhere a client can see.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
string

Rows whose name contains this text.

string
enum

Column to sort by; prefix with - to reverse it. Defaults to name.

Allowed:
integer

Which page to read.

integer

Rows per page, 25 by default and 100 at most. Anything that is not a positive whole number answers 400.

Response

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json