Minecraft status API documentation
Check Java and Bedrock servers, preserve the evidence boundary, and build against a versioned response contract.
Start with the task
- Java status APITCP status handshake, SRV resolution, counts, MOTD and reported version.
- Bedrock status APIRakNet unconnected ping, explicit ports, counts, MOTD and version.
- Runnable examplescURL, JavaScript, TypeScript, Python, PHP and Java with failure handling.
- Status badgesEmbed a cacheable SVG for a registered public target.
One request, one bounded observation
curl --fail-with-body \
-H 'Accept: application/json' \
'https://minecraftstatus.com/api/v1/status/java?address=play.example.net'Contract boundary
Responses carry observedAt, validUntil, freshness and the canonical evidenceCode. When validUntil has passed, preserve the target but treat the current verdict as Unknown until a new observation arrives.
Contract and limits
The generated OpenAPI 3.1 document is the machine-readable route register. Anonymous v1 requests allow 30 requests per minute and 5,000 target-observation units per day. Registered developer keys allow 120 requests per minute and 100,000 units per day. Batch requests charge one unit per input target; polling a job does not charge another target unit.
Contract artifact SHA-256: b46a1723a698ea8a9d8743fe5c5c1c983ecdedc43f4630f112c862d85731f065
See the full API landing page or run a browser-safe request.