Personas API
A persona is an archetypal user the project is built for: a named, sketched person with goals, frustrations and habits, so the analyst, the developers and the testers picture the same someone.
A persona is an archetypal user the project is built for: a named, sketched person with goals, frustrations and habits, so the analyst, the developers and the testers picture the same someone. Personas are the "as a …" of user stories and the actors of use cases; a persona that falls out of use is archived so those references keep resolving. The four prose fields and the devices are the analyst's sketch, and Heimdall reads them when it drafts stories and tests.
The reads here see the personas of the projects the token may see, a client guest's token among them, because a persona describes the client's own users. A persona outside that set is a 404 RESOURCE_NOT_FOUND, never a 403. Every write runs the same action the Personas page runs, under the project permissions, and announces itself as a persona.* event.
Endpoints
/v1/personas/{persona}Get a personaPATCH/v1/personas/{persona}Update a personaDELETE/v1/personas/{persona}Delete a personaGET/v1/personas/{persona}/revisionsList a persona's versionsGET/v1/personas/{persona}/revisions/{revision}Read one version of a personaGET/v1/projects/{project}/personasList personasPOST/v1/projects/{project}/personasCreate a personaPOST/v1/personas/{persona}/archiveArchive a personaPOST/v1/personas/{persona}/restoreRestore a personaPOST/v1/personas/{persona}/revisions/{revision}/restoreRestore a version of a personaRelated
How is this guide?
Last updated on