Read the document type definitions
Every document type CORA handles, each with its current definition (fields, mappings, rules), independent of any application or upload. CORA reads it before any upload to build and review one Blueprint per document type and definitionVersion.
The manifest and the
application bundle share documentTypeId,
documentTypeKey and the definition objects (DefinitionField, DefinitionMapping, DefinitionRule). For a
given documentTypeId and definitionVersion, the bundle (with include) returns the definition this route
returned for that version. One version per document type. Any change to an approved definition is a new
definitionVersion. A definition that is not approved can change without a new version; the bundle serves
it as definitionVersion: null. This route returns only the current version. The bundle serves the
current definition version for each document type. The version can change during an application when a
definition is updated; compare definitionVersion to pick the Blueprint; a definitionVersion with no
Blueprint: re-read the manifest. A document type with no approved definition has
definitionVersion: null. Fortress tells Fission Labs when a definition changes. There is no event for
it.
The response is a JSON array, one element per document type, with no envelope. The route takes no parameters.
The API key needs the compliance-documents: read permission.
Authenticate with the x-api-key header.
Authentication
Response
Current version of the definition. The bundle serves the current definition version for each
document type. The version can change during an application when a definition is updated; compare
definitionVersion to pick the Blueprint; a definitionVersion with no Blueprint: re-read the
manifest. A document type with no approved definition has definitionVersion: null.
Authoring status of this definitionVersion (authoring template, tab 1). Fortress is still aligning with Fission Labs (CORA) on which statuses the bundle serves.

