Overview

GDBrowser API provides a simple interface to the Geometry Dash game servers, letting you fetch level data, player profiles, and leaderboard scores. No authentication is required, which makes it easy to start building fan tools and stat pages right away. It is a community-maintained API ideal for Geometry Dash enthusiasts learning about REST APIs.

Beginner Tip

The API wraps the official Geometry Dash servers, so response times can vary. Cache results locally when possible to reduce load and improve your app speed.

Available Data

IP address details
latitude and longitude
city and country
timezone
ISP information

Example Response

JSON Response
{
  "id": 1,
  "name": "GDBrowser",
  "data": "Easy way to use the Geometry Dash Servers",
  "source": "GDBrowser"
}

Field Reference

id Unique Geometry Dash level or player ID
name Name of the level or username of the player
author Username of the player who created the level
difficulty Difficulty rating of the level, e.g. Hard, Insane, Demon
stars Star rating awarded to the level by the Geometry Dash team

Implementation Example

Request
// ⚠️ Note: This URL may be a documentation page. Check official docs for actual API endpoint.
const url = "https://gdbrowser.com/api";
const response = await fetch(url);
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

-1 response body The Geometry Dash server returned an error or the requested resource was not found
Verify the level name or player username exists in-game before querying the API
Request timeout The upstream Geometry Dash server is slow to respond
Implement a timeout of at least 10 seconds in your HTTP client and add retry logic
Empty results array The search query returned no matching levels or players
Try broader search terms or check that the difficulty and type parameters use correct numeric values

Metadata Score Breakdown

Estimated from metadata — endpoint not independently tested

This score is estimated from observable metadata — HTTPS support, authentication model, declared CORS, and documentation reachability — because the API requires authentication or exposes no publicly testable endpoint. The five-signal breakdown is only shown for live-tested APIs.

Metadata estimate · endpoint not independently tested

Technical Specifications

Auth No Auth
HTTPS REQUIRED
CORS UNKNOWN
Category Games & Comics
Difficulty Beginner
Verified: 2026-04-04

Related Tags

Similar APIs

View All →