Action Logs
Bitbucket Server
Catalog News Articles
Catalog Technologies
Code Repos
Comment Replies
Diagram Contents
Diagrams
Flows
Health
Landscape Templates
Landscape Thumbnails
Model Connections
Model Objects
News
Organization Billing
Organization Icons
Organization Landscapes
Organizations
Organization Technologies
Organization User Invites
Organization Users
Share Link
Share Link Options
Support
User
User Notifications
User Goals
Version Reverts
Create
Headers
Path Parameters
Body
The parts of the format that's common to all versions/kinds of entity.
Metadata fields common to all versions/kinds of entity.
The name of the entity. Must be unique within the catalog at any given point in time, for any given namespace + kind pair.
A globally unique ID for the entity. This field can not be set by the user at creation time, and the server will reject an attempt to do so. The field will be populated in read operations. The field can (optionally) be specified when performing update or delete operations, but the server is free to reject requests that do so in such a way that it breaks semantics.
An opaque string that changes for each update operation to any part of the entity, including metadata. This field can not be set by the user at creation time, and the server will reject an attempt to do so. The field will be populated in read operations. The field can (optionally) be specified when performing update or delete operations, and the server will then reject the operation if it does not match the current stored value.
The namespace that the entity belongs to.
A display name of the entity, to be presented in user interfaces instead of the name property, when available.
A short (typically relatively few words, on one line) description of the entity.
Key/value pairs of identifying information attached to the entity.
Key/value pairs of non-identifying auxiliary information attached to the entity.
A list of single-valued strings, to for example classify catalog entities in various ways.
A list of external hyperlinks related to the entity. Links can provide additional contextual information that may be located outside of Backstage itself. For example, an admin dashboard or external CMS page.
A url in a standard uri format.
A user friendly display name for the link.
A key representing a visual icon to be displayed in the UI.
An optional value to categorize links into specific groups.
backstage.io/v1alpha1, backstage.io/v1beta1 API The type of the API definition.
The lifecycle state of the API.
An entity reference to the owner of the API.
The definition of the API, based on the format defined by the type.
An entity reference to the system that the API belongs to.
The relations that this entity has with other entities.
The type of relation.
A reference by name to another entity.
The entity ref of the target of this relation.
The current status of the entity, as claimed by various sources.
The status level / severity of the status item.
info, warning, error A brief message describing the status, intended for human consumption.
An optional serialized error object related to the status.
Metadata fields common to all versions/kinds of entity.
The name of the entity. Must be unique within the catalog at any given point in time, for any given namespace + kind pair.
A globally unique ID for the entity. This field can not be set by the user at creation time, and the server will reject an attempt to do so. The field will be populated in read operations. The field can (optionally) be specified when performing update or delete operations, but the server is free to reject requests that do so in such a way that it breaks semantics.
An opaque string that changes for each update operation to any part of the entity, including metadata. This field can not be set by the user at creation time, and the server will reject an attempt to do so. The field will be populated in read operations. The field can (optionally) be specified when performing update or delete operations, and the server will then reject the operation if it does not match the current stored value.
The namespace that the entity belongs to.
A display name of the entity, to be presented in user interfaces instead of the name property, when available.
A short (typically relatively few words, on one line) description of the entity.
Key/value pairs of identifying information attached to the entity.
Key/value pairs of non-identifying auxiliary information attached to the entity.
A list of single-valued strings, to for example classify catalog entities in various ways.
A list of external hyperlinks related to the entity. Links can provide additional contextual information that may be located outside of Backstage itself. For example, an admin dashboard or external CMS page.
A url in a standard uri format.
A user friendly display name for the link.
A key representing a visual icon to be displayed in the UI.
An optional value to categorize links into specific groups.
backstage.io/v1alpha1, backstage.io/v1beta1 Component The type of component.
The lifecycle state of the component.
An entity reference to the owner of the component.
An entity reference to the system that the component belongs to.
An entity reference to another component of which the component is a part.
An array of entity references to the APIs that are provided by the component.
An array of entity references to the APIs that are consumed by the component.
An array of references to other entities that the component depends on to function.
The relations that this entity has with other entities.
The type of relation.
A reference by name to another entity.
The kind field of the entity.
The metadata.namespace field of the entity.
The metadata.name field of the entity.
The entity ref of the target of this relation.
The current status of the entity, as claimed by various sources.
The status level / severity of the status item.
info, warning, error A brief message describing the status, intended for human consumption.
An optional serialized error object related to the status.
Metadata fields common to all versions/kinds of entity.
The name of the entity. Must be unique within the catalog at any given point in time, for any given namespace + kind pair.
A globally unique ID for the entity. This field can not be set by the user at creation time, and the server will reject an attempt to do so. The field will be populated in read operations. The field can (optionally) be specified when performing update or delete operations, but the server is free to reject requests that do so in such a way that it breaks semantics.
An opaque string that changes for each update operation to any part of the entity, including metadata. This field can not be set by the user at creation time, and the server will reject an attempt to do so. The field will be populated in read operations. The field can (optionally) be specified when performing update or delete operations, and the server will then reject the operation if it does not match the current stored value.
The namespace that the entity belongs to.
A display name of the entity, to be presented in user interfaces instead of the name property, when available.
A short (typically relatively few words, on one line) description of the entity.
Key/value pairs of identifying information attached to the entity.
Key/value pairs of non-identifying auxiliary information attached to the entity.
A list of single-valued strings, to for example classify catalog entities in various ways.
A list of external hyperlinks related to the entity. Links can provide additional contextual information that may be located outside of Backstage itself. For example, an admin dashboard or external CMS page.
A url in a standard uri format.
A user friendly display name for the link.
A key representing a visual icon to be displayed in the UI.
An optional value to categorize links into specific groups.
backstage.io/v1alpha1, backstage.io/v1beta1 Domain An entity reference to the owner of the component.
The relations that this entity has with other entities.
The type of relation.
A reference by name to another entity.
The kind field of the entity.
The metadata.namespace field of the entity.
The metadata.name field of the entity.
The entity ref of the target of this relation.
The current status of the entity, as claimed by various sources.
The status level / severity of the status item.
info, warning, error A brief message describing the status, intended for human consumption.
An optional serialized error object related to the status.
Metadata fields common to all versions/kinds of entity.
The name of the entity. Must be unique within the catalog at any given point in time, for any given namespace + kind pair.
A globally unique ID for the entity. This field can not be set by the user at creation time, and the server will reject an attempt to do so. The field will be populated in read operations. The field can (optionally) be specified when performing update or delete operations, but the server is free to reject requests that do so in such a way that it breaks semantics.
An opaque string that changes for each update operation to any part of the entity, including metadata. This field can not be set by the user at creation time, and the server will reject an attempt to do so. The field will be populated in read operations. The field can (optionally) be specified when performing update or delete operations, and the server will then reject the operation if it does not match the current stored value.
The namespace that the entity belongs to.
A display name of the entity, to be presented in user interfaces instead of the name property, when available.
A short (typically relatively few words, on one line) description of the entity.
Key/value pairs of identifying information attached to the entity.
Key/value pairs of non-identifying auxiliary information attached to the entity.
A list of single-valued strings, to for example classify catalog entities in various ways.
A list of external hyperlinks related to the entity. Links can provide additional contextual information that may be located outside of Backstage itself. For example, an admin dashboard or external CMS page.
A url in a standard uri format.
A user friendly display name for the link.
A key representing a visual icon to be displayed in the UI.
An optional value to categorize links into specific groups.
backstage.io/v1alpha1, backstage.io/v1beta1 Resource The type of resource.
An entity reference to the owner of the resource.
An array of references to other entities that the resource depends on to function.
An entity reference to the system that the resource belongs to.
The relations that this entity has with other entities.
The type of relation.
A reference by name to another entity.
The kind field of the entity.
The metadata.namespace field of the entity.
The metadata.name field of the entity.
The entity ref of the target of this relation.
The current status of the entity, as claimed by various sources.
The status level / severity of the status item.
info, warning, error A brief message describing the status, intended for human consumption.
An optional serialized error object related to the status.
Metadata fields common to all versions/kinds of entity.
The name of the entity. Must be unique within the catalog at any given point in time, for any given namespace + kind pair.
A globally unique ID for the entity. This field can not be set by the user at creation time, and the server will reject an attempt to do so. The field will be populated in read operations. The field can (optionally) be specified when performing update or delete operations, but the server is free to reject requests that do so in such a way that it breaks semantics.
An opaque string that changes for each update operation to any part of the entity, including metadata. This field can not be set by the user at creation time, and the server will reject an attempt to do so. The field will be populated in read operations. The field can (optionally) be specified when performing update or delete operations, and the server will then reject the operation if it does not match the current stored value.
The namespace that the entity belongs to.
A display name of the entity, to be presented in user interfaces instead of the name property, when available.
A short (typically relatively few words, on one line) description of the entity.
Key/value pairs of identifying information attached to the entity.
Key/value pairs of non-identifying auxiliary information attached to the entity.
A list of single-valued strings, to for example classify catalog entities in various ways.
A list of external hyperlinks related to the entity. Links can provide additional contextual information that may be located outside of Backstage itself. For example, an admin dashboard or external CMS page.
A url in a standard uri format.
A user friendly display name for the link.
A key representing a visual icon to be displayed in the UI.
An optional value to categorize links into specific groups.
backstage.io/v1alpha1, backstage.io/v1beta1 System The relations that this entity has with other entities.
The type of relation.
A reference by name to another entity.
The kind field of the entity.
The metadata.namespace field of the entity.
The metadata.name field of the entity.
The entity ref of the target of this relation.
The current status of the entity, as claimed by various sources.
The status level / severity of the status item.
info, warning, error A brief message describing the status, intended for human consumption.
An optional serialized error object related to the status.
Represents a Structurizr workspace, which is a wrapper for a software architecture model, views, and documentation.
The workspace ID.
The name of the workspace.
A short description of the workspace.
A version number for the workspace.
The thumbnail associated with the workspace; a Base64 encoded PNG file as a data URI (data:image/png;base64).
The last modified date, in ISO 8601 format (e.g. "2018-09-08T12:40:03Z").
A string identifying the user who last modified the workspace (e.g. an e-mail address or username).
A string identifying the agent that was last used to modify the workspace (e.g. "structurizr-java/1.2.0").
A software architecture model.
The enterprise associated with this model.
The name of the enterprise.
The ID of this person in the model.
The name of this person.
A short description of this person.
A comma separated list of tags associated with this person.
The URL where more information about this element can be found.
The location of this person.
External, Internal, Unspecified The name of the group in which this person should be included in.
A set of arbitrary name-value properties.
The set of relationships from this person to other elements.
The ID of this relationship in the model.
A short description of this relationship.
A comma separated list of tags associated with this relationship.
The URL where more information about this relationship can be found.
The ID of the source element.
The ID of the destination element.
The technology associated with this relationship (e.g. HTTPS, JDBC, etc).
The interaction style (synchronous or asynchronous).
Synchronous, Asynchronous The ID of the container-container relationship upon which this container instance-container instance relationship is based.
The ID of this software system in the model.
The name of this software system.
A short description of this software system.
The location of this software system.
External, Internal, Unspecified A comma separated list of tags associated with this software system.
The URL where more information about this element can be found.
The set of containers within this software system.
The ID of this container in the model.
The name of this container.
A short description of this container.
The technology associated with this container (e.g. Apache Tomcat).
A comma separated list of tags associated with this container.
The URL where more information about this element can be found.
The set of components within this container.
The name of the group in which this container should be included in.
A set of arbitrary name-value properties.
The set of relationships from this container to other elements.
A wrapper for documentation.
The name of the group in which this software system should be included in.
A set of arbitrary name-value properties.
The set of relationships from this software system to other elements.
The ID of this relationship in the model.
A short description of this relationship.
A comma separated list of tags associated with this relationship.
The URL where more information about this relationship can be found.
The ID of the source element.
The ID of the destination element.
The technology associated with this relationship (e.g. HTTPS, JDBC, etc).
The interaction style (synchronous or asynchronous).
Synchronous, Asynchronous The ID of the container-container relationship upon which this container instance-container instance relationship is based.
The ID of this deployment node in the model.
The name of this deployment node.
A short description of this deployment node.
The technology associated with this deployment node (e.g. Apache Tomcat).
The deployment environment in which this deployment node resides (e.g. "Development", "Live", etc).
The number of instances; either a number (e.g. 1, 2, etc) or a range (e.g. 0..N, 0..*, 1..3, etc).
A comma separated list of tags associated with this deployment node.
The URL where more information about this element can be found.
The set of child/nested deployment nodes.
The ID of this deployment node in the model.
The name of this deployment node.
A short description of this deployment node.
The technology associated with this deployment node (e.g. Apache Tomcat).
The deployment environment in which this deployment node resides (e.g. "Development", "Live", etc).
The number of instances; either a number (e.g. 1, 2, etc) or a range (e.g. 0..N, 0..*, 1..3, etc).
A comma separated list of tags associated with this deployment node.
The URL where more information about this element can be found.
The set of child/nested deployment nodes.
The set of software systems instances running in this deployment node..
The set of container instances running in this deployment node..
A set of arbitrary name-value properties.
The set of relationships from this deployment node to other elements.
The ID of this infrastructure node in the model.
The name of this infrastructure node.
A short description of this infrastructure node.
The technology associated with this infrastructure node (e.g. "Route 53").
The deployment environment in which this infrastructure node resides (e.g. "Development", "Live", etc).
A comma separated list of tags associated with this infrastructure node.
The URL where more information about this element can be found.
A set of arbitrary name-value properties.
The set of relationships from this infrastructure node to other elements.
The set of software systems instances running in this deployment node..
The ID of this software system instance in the model.
The ID of the software system this is an instance of.
The number/index of this instance.
The deployment environment in which this software system instance resides (e.g. "Development", "Live", etc).
A comma separated list of tags associated with this software system instance.
A set of arbitrary name-value properties.
The set of relationships from this software system instance to other elements.
The set of HTTP-based health checks for this software system instance.
The set of container instances running in this deployment node..
The ID of this container instance in the model.
The ID of the container this is an instance of.
The number/index of this instance.
The deployment environment in which this container instance resides (e.g. "Development", "Live", etc).
A comma separated list of tags associated with this container instance.
A set of arbitrary name-value properties.
The set of relationships from this container instance to other elements.
The set of HTTP-based health checks for this container instance.
A set of arbitrary name-value properties.
The set of relationships from this deployment node to other elements.
The ID of this relationship in the model.
A short description of this relationship.
A comma separated list of tags associated with this relationship.
The URL where more information about this relationship can be found.
The ID of the source element.
The ID of the destination element.
The technology associated with this relationship (e.g. HTTPS, JDBC, etc).
The interaction style (synchronous or asynchronous).
Synchronous, Asynchronous The ID of the container-container relationship upon which this container instance-container instance relationship is based.
The set of views onto a software architecture model.
The set of system landscape views.
The title of this view (optional).
The description of this view.
A unique identifier for this view.
The paper size that should be used to render this view.
A6_Portrait, A6_Landscape, A5_Portrait, A5_Landscape, A4_Portrait, A4_Landscape, A3_Portrait, A3_Landscape, A2_Portrait, A2_Landscape, A1_Portrait, A1_Landscape, A0_Portrait, A0_Landscape, Letter_Portrait, Letter_Landscape, Legal_Portrait, Legal_Landscape, Slide_4_3, Slide_16_9, Slide_16_10 Represents the auto-layout configuration for a given view.
The algorithm rank direction.
TopBottom, BottomTop, LeftRight, RightLeft The separation between ranks (pixels).
The separation between nodes in the same rank (pixels).
The separation between edges (pixels).
Whether vertices should be created during automatic layout.
Specifies whether the enterprise boundary (to differentiate internal elements from external elements) should be visible on the resulting diagram.
The set of elements in this views.
The ID of the element.
The horizontal position of the element when rendered.
The vertical position of the element when rendered.
The set of relationships in this views.
The ID of the relationship.
The description of this relationship (used in dynamic views only).
Signifies whether this relationship represents a return/response message (used in dynamic views only).
Gets the order of this relationship (used in dynamic views only; e.g. 1.0, 1.1, 2.0, etc).
The set of vertices used to render the relationship.
The routing algorithm used when rendering this individual relationship.
Direct, Curved, Orthogonal The position of the annotation along the line; 0 (start) to 100 (end).
The set of animation steps (optional).
The order of this animation step.
The set of element IDs that should be included in this animation step.
The set of relationship IDs that should be included in this animation step.
The set of system context views.
The title of this view (optional).
The description of this view.
A unique identifier for this view.
The ID of the software system this view is associated with.
The paper size that should be used to render this view.
A6_Portrait, A6_Landscape, A5_Portrait, A5_Landscape, A4_Portrait, A4_Landscape, A3_Portrait, A3_Landscape, A2_Portrait, A2_Landscape, A1_Portrait, A1_Landscape, A0_Portrait, A0_Landscape, Letter_Portrait, Letter_Landscape, Legal_Portrait, Legal_Landscape, Slide_4_3, Slide_16_9, Slide_16_10 Represents the auto-layout configuration for a given view.
The algorithm rank direction.
TopBottom, BottomTop, LeftRight, RightLeft The separation between ranks (pixels).
The separation between nodes in the same rank (pixels).
The separation between edges (pixels).
Whether vertices should be created during automatic layout.
Specifies whether the enterprise boundary (to differentiate internal elements from external elements") should be visible on the resulting diagram.
The set of elements in this view.
The ID of the element.
The horizontal position of the element when rendered.
The vertical position of the element when rendered.
The set of relationships in this view.
The ID of the relationship.
The description of this relationship (used in dynamic views only).
Signifies whether this relationship represents a return/response message (used in dynamic views only).
Gets the order of this relationship (used in dynamic views only; e.g. 1.0, 1.1, 2.0, etc).
The set of vertices used to render the relationship.
The routing algorithm used when rendering this individual relationship.
Direct, Curved, Orthogonal The position of the annotation along the line; 0 (start) to 100 (end).
The set of animation steps (optional).
The order of this animation step.
The set of element IDs that should be included in this animation step.
The set of relationship IDs that should be included in this animation step.
The set of container views.
The title of this view (optional).
The description of this view.
A unique identifier for this view.
The ID of the software system this view is associated with.
The paper size that should be used to render this view.
A6_Portrait, A6_Landscape, A5_Portrait, A5_Landscape, A4_Portrait, A4_Landscape, A3_Portrait, A3_Landscape, A2_Portrait, A2_Landscape, A1_Portrait, A1_Landscape, A0_Portrait, A0_Landscape, Letter_Portrait, Letter_Landscape, Legal_Portrait, Legal_Landscape, Slide_4_3, Slide_16_9, Slide_16_10 Represents the auto-layout configuration for a given view.
The algorithm rank direction.
TopBottom, BottomTop, LeftRight, RightLeft The separation between ranks (pixels).
The separation between nodes in the same rank (pixels).
The separation between edges (pixels).
Whether vertices should be created during automatic layout.
The set of elements in this views.
The ID of the element.
The horizontal position of the element when rendered.
The vertical position of the element when rendered.
The set of relationships in this views.
The ID of the relationship.
The description of this relationship (used in dynamic views only).
Signifies whether this relationship represents a return/response message (used in dynamic views only).
Gets the order of this relationship (used in dynamic views only; e.g. 1.0, 1.1, 2.0, etc).
The set of vertices used to render the relationship.
The routing algorithm used when rendering this individual relationship.
Direct, Curved, Orthogonal The position of the annotation along the line; 0 (start) to 100 (end).
The set of animation steps (optional).
The order of this animation step.
The set of element IDs that should be included in this animation step.
The set of relationship IDs that should be included in this animation step.
Specifies whether software system boundaries should be visible for "external" containers (those outside the software system in scope).
The set of component views.
The title of this view (optional).
The description of this view.
A unique identifier for this view.
The ID of the container this view is associated with.
The paper size that should be used to render this view.
A6_Portrait, A6_Landscape, A5_Portrait, A5_Landscape, A4_Portrait, A4_Landscape, A3_Portrait, A3_Landscape, A2_Portrait, A2_Landscape, A1_Portrait, A1_Landscape, A0_Portrait, A0_Landscape, Letter_Portrait, Letter_Landscape, Legal_Portrait, Legal_Landscape, Slide_4_3, Slide_16_9, Slide_16_10 Represents the auto-layout configuration for a given view.
The algorithm rank direction.
TopBottom, BottomTop, LeftRight, RightLeft The separation between ranks (pixels).
The separation between nodes in the same rank (pixels).
The separation between edges (pixels).
Whether vertices should be created during automatic layout.
The set of elements in this views.
The ID of the element.
The horizontal position of the element when rendered.
The vertical position of the element when rendered.
The set of relationships in this views.
The ID of the relationship.
The description of this relationship (used in dynamic views only).
Signifies whether this relationship represents a return/response message (used in dynamic views only).
Gets the order of this relationship (used in dynamic views only; e.g. 1.0, 1.1, 2.0, etc).
The set of vertices used to render the relationship.
The routing algorithm used when rendering this individual relationship.
Direct, Curved, Orthogonal The position of the annotation along the line; 0 (start) to 100 (end).
The set of animation steps (optional).
The order of this animation step.
The set of element IDs that should be included in this animation step.
The set of relationship IDs that should be included in this animation step.
Specifies whether container boundaries should be visible for "external" components (those outside the container in scope).
The set of dynamic views.
The title of this view (optional).
The description of this view.
An identifier for this view.
The ID of the element this view is associated with (optional).
The paper size that should be used to render this view.
A6_Portrait, A6_Landscape, A5_Portrait, A5_Landscape, A4_Portrait, A4_Landscape, A3_Portrait, A3_Landscape, A2_Portrait, A2_Landscape, A1_Portrait, A1_Landscape, A0_Portrait, A0_Landscape, Letter_Portrait, Letter_Landscape, Legal_Portrait, Legal_Landscape, Slide_4_3, Slide_16_9, Slide_16_10 Represents the auto-layout configuration for a given view.
The algorithm rank direction.
TopBottom, BottomTop, LeftRight, RightLeft The separation between ranks (pixels).
The separation between nodes in the same rank (pixels).
The separation between edges (pixels).
Whether vertices should be created during automatic layout.
The set of elements in this views.
The ID of the element.
The horizontal position of the element when rendered.
The vertical position of the element when rendered.
The set of relationships in this views.
The ID of the relationship.
The description of this relationship (used in dynamic views only).
Signifies whether this relationship represents a return/response message (used in dynamic views only).
Gets the order of this relationship (used in dynamic views only; e.g. 1.0, 1.1, 2.0, etc).
The set of vertices used to render the relationship.
The routing algorithm used when rendering this individual relationship.
Direct, Curved, Orthogonal The position of the annotation along the line; 0 (start) to 100 (end).
Specifies software system/container boundaries should be visible for "external" containers/components (those outside the element in scope)
The set of deployment views.
The title of this view (optional).
The description of this view.
A unique identifier for this view.
The ID of the software system this view is associated with (optional).
The name of the environment that this deployment view is for (e.g. "Development", "Live", etc).
The paper size that should be used to render this view.
A6_Portrait, A6_Landscape, A5_Portrait, A5_Landscape, A4_Portrait, A4_Landscape, A3_Portrait, A3_Landscape, A2_Portrait, A2_Landscape, A1_Portrait, A1_Landscape, A0_Portrait, A0_Landscape, Letter_Portrait, Letter_Landscape, Legal_Portrait, Legal_Landscape, Slide_4_3, Slide_16_9, Slide_16_10 Represents the auto-layout configuration for a given view.
The algorithm rank direction.
TopBottom, BottomTop, LeftRight, RightLeft The separation between ranks (pixels).
The separation between nodes in the same rank (pixels).
The separation between edges (pixels).
Whether vertices should be created during automatic layout.
The set of elements in this views.
The ID of the element.
The horizontal position of the element when rendered.
The vertical position of the element when rendered.
The set of relationships in this views.
The ID of the relationship.
The description of this relationship (used in dynamic views only).
Signifies whether this relationship represents a return/response message (used in dynamic views only).
Gets the order of this relationship (used in dynamic views only; e.g. 1.0, 1.1, 2.0, etc).
The set of vertices used to render the relationship.
The routing algorithm used when rendering this individual relationship.
Direct, Curved, Orthogonal The position of the annotation along the line; 0 (start) to 100 (end).
The set of animation steps (optional).
The order of this animation step.
The set of element IDs that should be included in this animation step.
The set of relationship IDs that should be included in this animation step.
The set of filtered views.
The title of this view (optional).
The description of this view.
A unique identifier for this view.
The key of the view on which this filtered view is based.
Whether elements/relationships are being included or excluded based upon the set of tags.
Include, Exclude The set of tags to include/exclude elements/relationships when rendering this filtered view.
The configuration associated with a set of views.
The key of the view that was saved most recently.
The key of the view that should be shown by default.
The URL(s) of the theme(s) to be used when rendering diagrams.
A wrapper for the font and logo for diagram/documentation branding purposes.
Provides a way for the terminology on diagrams, etc to be modified (e.g. language translations).
The terminology used when rendering the enterprise boundary.
The terminology used when rendering people.
The terminology used when rendering software systems.
The terminology used when rendering containers.
The terminology used when rendering components.
The terminology used when rendering code elements.
The terminology used when rendering deployment nodes.
The terminology used when rendering relationships.
The type of symbols to use when rendering metadata.
SquareBrackets, RoundBrackets, CurlyBrackets, AngleBrackets, DoubleAngleBrackets, None A wrapper for documentation.
The Markdown or AsciiDoc content of the section.
The content format type.
Markdown, AsciiDoc The order (index) of the section in the document.
The ID of the decision.
The date that the decision was made (ISO 8601 format).
The status of the decision.
Proposed, Accepted, Superseded, Deprecated, Rejected The title of the decision.
The Markdown or AsciiDoc content of the section.
The content format type.
Markdown, AsciiDoc The ID of the element (in the model) that this decision applies to (optional).
A set of arbitrary name-value properties.
Response
user, api-key, notification-key, service user, api-key, notification-key, service 110user, api-key, notification-key, service user, api-key, notification-key, service