Alias table — JSON
const url = 'https://textrefs.org/dump/aliases.json';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://textrefs.org/dump/aliases.jsonThe complete alias table as one JSON object, with sorted keys and no indentation. For a single lookup, use /reg/work/{key}/aliases.json instead. This file serves a consumer that mirrors the whole table.
Responses
Section titled “Responses”One JSON object. Each key is an alias. Each value is the canonical IRI that the alias resolves to.
The /dump/aliases.json table, with one entry per alias. A key is either a /cite/ alias path — {work_key}/{locator} or {work_key}/{citation_system_key}/{locator} — or an external identifier IRI carried by a MappingAssertion. A value is the canonical IRI that the key resolves to — an /id/ref/ IRI for a /cite/ alias, an /id/work/ IRI for an external identifier. A :// in the key marks the second kind.
object
An IRI (RFC 3987), not a URI (RFC 3986). The registry publishes resolver targets that carry non-ASCII characters, such as …/Investigaciones_filosóficas_(edición_A). RFC 3986 forbids those characters, so a validator that enforces the uri format rejects records this site serves. The generated JSON Schema declares iri for the same reason.
Examplegenerated
{ "additionalProperty": "example"}