Browse all realms
const url = 'http://localhost:11044/api/v1/directory/browse/realms';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/directory/browse/realms \ --header 'X-Embabel-Api-Key: <X-Embabel-Api-Key>'Returns available realms grouped by provider/account. The complete field is false when a source scan failed or returned partial results.
Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”Realms grouped by provider
Every realm the directory knows, grouped by the account or organisation that publishes it
object
False when a source scan failed or returned partial results, so some realms may be missing
One group per publisher
The realms one publisher offers
object
The publishing account or organisation, from the entry’s from metadata, or “unknown”
That publisher’s realms
One installable realm as the browse lists it
object
What the realm is for, as its publisher describes it
True when a realm of this name is already loaded in the caller’s world
The source’s own extras for this realm, passed through as reported. Open by contract
object
The realm’s name, as an install names it
Where the realm installs from: a git clone URL or registry identifier
A human-readable page for the realm, or null when the source has none
Directory scan incomplete and no realms available; use Refresh directory to retry
The realm scan is incomplete and found nothing, so there is no partial catalogue to show
object
What to do about it, written to be shown