Describe one installed realm
const url = 'http://localhost:11044/api/v1/realms/example';const options = {method: 'GET', headers: {'X-Embabel-Api-Key': '<X-Embabel-Api-Key>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url http://localhost:11044/api/v1/realms/example \ --header 'X-Embabel-Api-Key: <X-Embabel-Api-Key>'The realm’s row from the same Realms view the listing reads, with the same held-back fields.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Realm name
Responses
Section titled “Responses”The realm
An installed realm as the Realms view lists it, with whether the world holds it back. A held-back realm stays installed and listed but offers nothing until the realms it requires are installed at versions it accepts
object
Who the realm says published it; empty when unstated
The id of the category it says it belongs to; empty when it names none on the list
The category’s icon name; empty when it has none
The category’s name for people; empty when category is
What the realm says it is for; empty when it says nothing
True while the world holds the realm back because a realm it requires is missing, held back, or at a version it does not accept
The problem code that holds it back, such as REALM_REQUIREMENT_MISSING; absent when it is not held back
The sentence of that problem, the same one the realm’s problems carry; absent when it is not held back
Where to fetch the realm’s icon; empty when it has none
Always true here: only installed realms are listed
The directory’s version when it knows this realm; empty otherwise
experimental, beta, stable or deprecated; empty when unstated
Datasources it names that the world does not declare
The realm’s name, which every other realm route is keyed by
How many problems were found loading it; GET /realms/{name}/problems lists them
The account the directory says hosts it; empty when the directory does not know it
Where the directory says to install it from; empty when it does not know it
Free-text keywords from the realm
A page to read about it; empty when there is none
The version installed
No installed realm has that name. Raised as a status, so it answers the not-found page
The Realms view is unavailable, or the engine read failed
The body the servlet error dispatch answers for a status raised by an exception rather than written by the endpoint. Every failure except 404, which answers the not-found HTML page
object
The status’s standard reason phrase, such as Bad Request or Forbidden
The request path that failed
The HTTP status code, repeated from the status line

