Developer
Get Support
Sign in
Get Support
Sign in
DOCUMENTATION
Cloud
Data Center
Resources
Sign in
Sign in
DOCUMENTATION
Cloud
Data Center
Resources
Sign in
Object types
Relationship types
Last updated Jan 8, 2026

Confluence blog post

The Teamwork Graph API is available through Forge's Early Access Program (EAP).

EAPs are offered to selected users for testing and feedback purposes. These features are unsupported and are subject to change without notice.

You must only install apps that call the Teamwork Graph API in test organizations. Apps calling the Teamwork Graph API require the read:graph:jiraor read:graph:confluence scope, which provides access to Teamwork Graph data across your entire organization. While apps still respect end-user permissions, this scope may grant access to sensitive information. For safety, only install these apps in organizations with test data. Do not install apps using this API in organizations with production data while this feature is in EAP.

Additionally, this EAP has significant limitations. To review the full list of limitations, see Limitations and considerations.

You must be part of this EAP in order to use the Teamwork Graph API. Express interest in joining through this form.

Represents a Confluence blog post - a time-ordered publication within a Confluence space. Blog posts are used for announcements, updates, team communications, and time-sensitive content that follows a chronological publishing pattern.

Available fields and properties

The Teamwork Graph API has the following fields and properties that you can use in your queries:

  • Object type fields are the core data fields of the object. Use these when you want to retrieve specific information about the object in your queries.
  • Cypher query properties are metadata properties used for filtering and traversing relationships between different object types in Teamwork Graph. Use Cypher query properties when you need to filter or navigate relationships between this object and other objects in your queries.

Object type fields

You can access these fields in the GraphiQL playground using the book icon in the top left, and then searching for Confluence blog post.

FieldTypeDescription
authorUserUser who authored this blog post.
contentConfluenceBodiesContent body of the blog post in various format representations. Confluence stores content in multiple formats to support different use cases and integrations.
createdAtDateTimeTimestamp when the blog post was originally created or first published.
idID!Unique identifier for the Confluence blog post. This ID is globally unique across the entire Teamwork Graph.
lastEditorUserUser who last edited this blog post.
lastUpdatedAtDateTimeTimestamp of the most recent modification to the blog post content or metadata.
ownerUserUser who owns this blog post.
spaceConfluenceSpaceThe Confluence space that contains this blog post. Provides context and navigation capabilities to the parent space.
statusConfluenceContentStatusCurrent publication status of the blog post, indicating its lifecycle state and visibility.
titleStringTitle of the blog post as displayed in feeds and the blog archive.

Fields for ConfluenceBodies

FieldTypeDescription
atlasDocFormatConfluenceBodyContent in ATLAS_DOC_FORMAT representation.

This format is optimized for modern Confluence editing and rendering experiences. It provides a structured document model that supports rich content types, collaborative editing features, and advanced layout capabilities.

storageConfluenceBodyContent in STORAGE format representation.

This is Confluence's native storage format that preserves the complete content structure including macros, formatting, and metadata. It's the authoritative representation used for persistence and serves as the source of truth for content.


Fields for ConfluenceBody

FieldTypeDescription
representationStringIdentifier for the content representation format.
valueStringThe actual content data in the format specified by the representation field.

Fields for ConfluenceBody

FieldTypeDescription
representationStringIdentifier for the content representation format.
valueStringThe actual content data in the format specified by the representation field.

Fields for ConfluenceSpace

FieldTypeDescription
aliasStringAlternative identifier or short name for the space. Provides additional flexibility in referencing and organizing spaces.
createdAtDateTimeTimestamp when the space was originally created.
creatorUserUser who originally created this space.
descriptionStringDescriptive text explaining the purpose and scope of the space. Helps users understand the space's content and intended use.
idID!Unique identifier for the Confluence space. This ID is globally unique across the entire Teamwork Graph. Format: ConfluenceSpaceARI
keyStringShort, URL-friendly key that uniquely identifies the space within a Confluence instance. Used in URLs and as a human-readable identifier (e.g., "TEAM" or "DOCS").
nameStringDisplay name of the space as shown in the UI and navigation. This is the primary human-readable identifier for the space.
statusConfluenceSpaceStatusCurrent lifecycle status of the space. Indicates whether the space is active (CURRENT) or has been archived (ARCHIVED).
typeConfluenceSpaceTypeClassification of the space's scope and ownership. GLOBAL spaces are shared team spaces, while PERSONAL spaces belong to individual users.
webUrlURLLinks associated with the Space.

Values for ConfluenceSpaceStatus

ValueDescription
ARCHIVEDSpace has been archived and is no longer actively used. Archived spaces are preserved but hidden from normal navigation. Content remains accessible but the space is marked as inactive.
CURRENTSpace is currently active and in normal use. This is the default state for spaces that are actively being used for collaboration.

Values for ConfluenceSpaceType

ValueDescription
GLOBALShared team space accessible to multiple users. Global spaces are used for team collaboration, documentation, and shared knowledge. Access is typically controlled through space permissions.
PERSONALPersonal space owned by an individual user. Personal spaces provide private areas for individual work, notes, and drafts. Typically visible only to the owner and explicitly granted users.

Values for ConfluenceContentStatus

ValueDescription
ARCHIVEDContent has been archived for long-term storage. Archived content is preserved but removed from normal navigation and search. Can be restored to CURRENT status if needed.
CURRENTContent is currently published and visible. This is the normal state for live content that users can view and interact with.
DELETEDContent has been permanently deleted. Deleted content is typically not recoverable through normal user actions. May be retained for audit or compliance purposes.
DRAFTContent is in draft state and not yet published. Draft content is only visible to its author and authorized collaborators. Can be published by changing status to CURRENT.
HISTORICALContent represents a historical version. Historical versions preserve content evolution and enable version comparison. Not directly visible but accessible through version history.
TRASHEDContent has been moved to trash but not permanently deleted. Trashed content can typically be restored or permanently deleted. Provides a safety net before permanent deletion.

Available relationships

The following relationships are currently supported for Confluence blog post:

Relationships where Confluence blog post is the source object.

Relationship nameFrom object typeTo object type
Confluence blogpost shared with Atlassian userConfluence blog postAtlassian user
Confluence blogpost has Confluence commentConfluence blog postConfluence comment
Entity links entityConfluence blog postConfluence page
Confluence blog post

Rate this page: