Overview

The Decentraland Places API provides programmatic access to scenes, worlds, and user interactions within Decentraland.

This API allows you to discover places in Genesis City and Decentraland Worlds, search for content, manage user favorites and ratings, and retrieve user activity data.

Authentication: Some endpoints require authentication using Decentraland's authentication system with Bearer tokens:

Authorization: Bearer <your-decentraland-auth-token>

Endpoints requiring authentication are marked with a πŸ”’ icon.

Response Format

All responses follow a consistent structure:

Success Response:

{
  "ok": true,
  "data": [...],
  "total": 100
}

Error Response:

{
  "ok": false,
  "error": "Error message description"
}

Coordinates Format

Parcel coordinates are represented as comma-separated integers: "x,y" (e.g., "-23,-96"). Valid range: -150 to 150 for both x and y coordinates.

Place ID Semantics

Each place has a persistent UUID that follows specific rules across scene redeployments:

UUID Preservation Rules:

A new scene deployment will keep the same UUID if it meets one of these criteria:

  • The new scene parcels contain every parcel from the previous scene (allows growing)

  • The new scene has the same base parcel as the previous scene (allows reshaping/shrinking)

A new deployment gets a new UUID when:

  • Moving to completely different parcels with a different base parcel

  • Shrinking without preserving the base parcel

Examples:

  • βœ… Same UUID: Expanding from 1 to 4 parcels (contains all previous)

  • βœ… Same UUID: Reshaping the scene but keeping the same base parcel

  • βœ… Same UUID: Shrinking but maintaining the same base parcel

  • ❌ New UUID: Moving to entirely different parcels with different base

  • ❌ New UUID: Shrinking and changing the base parcel

Why This Matters: This ensures user favorites, likes, and social data persist when scenes are updated, while creating new places when the scene fundamentally changes location.

Last updated