Read a personality's files
const url = 'http://localhost:11044/api/v1/world/personalities/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/world/personalities/example \ --header 'X-Embabel-Api-Key: <X-Embabel-Api-Key>'The identity and jinja sections of one personality, with whether it is editable. Realm personalities are readable but read-only — duplicating one into the world is how it becomes editable.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Slug of the personality to read, as listed by GET /world/personalities; any tier can be read. An unknown slug answers 404
Responses
Section titled “Responses”The personality’s files
object
Unknown personality
A refusal from the world administration surface: what went wrong, and the word error so a client reading the body need not consult the status code
object
What was refused and why, written to be shown. Names the offending value where there is one — the unknown mode, the out-of-range threshold, the invalid cron expression
Always error. Present because the map this replaces carried it and a consumer may branch on it
Example
error
