Feature Request: Include descriptive "hash names" (labels) in API responses with h=1

[neopterygii]

Feature Request: Include descriptive "hash names" (labels) in API responses with h=1

Background & Motivation

Currently, when using the h=1 parameter in API_GetGameList.php (or similar endpoints), the API returns only raw hash strings (e.g., MD5 checksums) under "Hashes". These values alone don’t clarify which ROM version or patch—like "USA No-Intro," "translation patch applied," or other good-tools-style labels—is associated with each hash.

To retrieve meaningful labels, developers must invoke a separate GetGameHashes endpoint for each game, which is slow and inefficient.

Proposed Solution

Enhance the existing h=1 functionality so that each game entry includes not only the raw hash values but also a descriptive label.

Example response structure:

"Hashes": [
  { "Hash": "8bd4a97783cda077c342173df0a9b51e", "Label": "USA – No-Intro" },
  { "Hash": "a13ab653a20fb383337fab1e52ddb0df", "Label": "European – Translation Patch" }
]

[wescopeland]

Unfortunately, we can't add any more fields to this endpoint. The response payload size for many game systems is already far too large.

I believe we should create an entirely new endpoint that is paginated (so we don't break clients currently relying on API_GetGameList.php). This would be more open to exposing other fields, such as labels, from our hashes database.