`enterDungeon`

Start matchmaking, or rejoin a run already in progress.

Blocks until matchmaking lands, which can take a while — this is not a fire-and-forget call. It auto-detects a mid-game account (`state` reports `reconnectPending`) and rejoins rather than queueing afresh. The reply names a game server, which is where the run happens; this API does not play it for you.

In Dungeons.

Request

POST /api/v1/sessions/{accountKey}/actions/enterDungeon

Parameters

Name	Type	Required	Description
`dungeonIdTag (dungeon_id_tag)`	string	no	Overrides the current selection.
`region`	integer	no	Overrides the current region.
`gameType`	integer	no	Normal, high-roller and so on.
`gearPoolIndex`	integer	no	Gear pool for the run.
`isRandom`	boolean	no	Let the server pick the dungeon.

Example request

{ "dungeonIdTag": "Goblin_Caves", "gameType": 1 }

Response

`{ ok: true, result, server, session, log, live }`.

Field	Type	Meaning
`server`	string	`ip:port` of the assigned game server.
`log`	string[]	What matchmaking did, step by step. Worth surfacing when it fails.
`live`	boolean	True when this rejoined a run already in progress rather than starting one.

Example response

{
  "ok": true,
  "result": "matched",
  "server": "203.0.113.40:7777",
  "session": "8f2c41e0-1c9a-4c2e-8b5a-9f1d2e3a4b5c",
  "log": ["region=1 set", "dungeon=Goblin_Caves gameType=1", "matched: 203.0.113.40:7777"],
  "live": false
}

Errors

Code	When
`action_failed`	The account is mid-game (abandon first), no character is in the lobby, or matchmaking produced no assignment — often a region that was never set.
`plan_limit`	Not on the free plan.

enterDungeon