🌍 Countries

Global territories for music distribution rights and regional content management

Resource Overview

Countries provide standardized territorial data for music distribution rights management and regional content control. This reference data enables precise geographical targeting for album distribution, territorial licensing, and compliance with regional music industry regulations. Countries are read-only reference data with continent relationships.

Base Endpoint
/countries
Resource Type
countries
Access Level
Read-only reference data

Schema

Read-only Attributes

Field Type Description
id string Unique identifier
name string Official country name (e.g., "United States", "Argentina")
alpha2-code string ISO 3166-1 alpha-2 country code (e.g., "US", "AR", "BR")

Relationships

Relationship Type Description
continent BelongsTo Geographic continent classification

Usage in Other Resources

🔗 Related Resources

  • • Albums: Distribution territories via many-to-many relationship
  • • Artists: Country of origin assignment
  • • Users: User location and phone country
  • • Continents: Geographic grouping for regional management
  • • Distribution Requests: Territorial specification for releases

List Countries

GET /countries Read Only 
GET /countries
Authorization: Bearer {token}
Accept: application/vnd.api+json

Query Parameters

Filtering

  • • filter[name] - Filter by country name
  • • filter[alpha2-code] - Filter by alpha-2 code
  • • filter[continent-id] - Filter by continent

Other Parameters

  • • include - Include continent data
  • • sort - Sort by name or code
  • • page[number] - Page number
  • • page[size] - Results per page

Example Request

GET /countries?include=continent&sort=name&page[size]=20

Success Response

200 OK 
{
  "data": [
    {
      "type": "countries",
      "id": "1",
      "attributes": {
        "name": "Argentina",
        "alpha2-code": "AR"
      },
      "relationships": {
        "continent": {
          "data": {"type": "continents", "id": "5"}
        }
      }
    },
    {
      "type": "countries",
      "id": "2",
      "attributes": {
        "name": "Brazil",
        "alpha2-code": "BR"
      },
      "relationships": {
        "continent": {
          "data": {"type": "continents", "id": "5"}
        }
      }
    },
    {
      "type": "countries",
      "id": "39",
      "attributes": {
        "name": "United States",
        "alpha2-code": "US"
      },
      "relationships": {
        "continent": {
          "data": {"type": "continents", "id": "2"}
        }
      }
    }
  ],
  "included": [
    {
      "type": "continents",
      "id": "2",
      "attributes": {
        "name": "NA"
      }
    },
    {
      "type": "continents",
      "id": "5",
      "attributes": {
        "name": "SA"
      }
    }
  ],
  "meta": {
    "page": {
      "current-page": 1,
      "per-page": 20,
      "total": 195,
      "last-page": 10
    }
  }
}

Get Single Country

GET /countries/{id} 
GET /countries/39?include=continent
Authorization: Bearer {token}
Accept: application/vnd.api+json

Success Response

200 OK 
{
  "data": {
    "type": "countries",
    "id": "39",
    "attributes": {
      "name": "United States",
      "alpha2-code": "US"
    },
    "relationships": {
      "continent": {
        "data": {"type": "continents", "id": "2"}
      }
    }
  },
  "included": [
    {
      "type": "continents",
      "id": "2",
      "attributes": {
        "name": "NA"
      }
    }
  ]
}

Integration Guidelines

💡 Best Practices

  • • Cache country data for optimal performance
  • • Use alpha-2 codes for standardization
  • • Include continent data for regional grouping
  • • Validate country IDs before assignment
  • • Consider territorial licensing requirements

✅ Distribution Strategy

  • • Major markets: US, UK, Germany, Japan
  • • Regional clusters for Latin America
  • • EU compliance for European territories
  • • Streaming platform territorial requirements
  • • Rights clearance per territory

⚠️ Important Notes

  • • Countries are read-only reference data
  • • Territory assignments affect distribution rights
  • • ISO 3166-1 alpha-2 standard compliance
  • • Regional licensing may vary by DSP

🌏 Global Reach

  • • 195+ countries supported worldwide
  • • Regional market optimization
  • • Territorial content compliance
  • • Multi-territory release coordination
  • • Global distribution network support