Space Properties

The space properties commands list key-value metadata stored on a Confluence space. Properties are typically created by apps, integrations, or administrators to attach structured data to a space.

These commands are useful when you need to understand what else is attached to a space besides the visible page tree.

Properties by key


acs2md space properties by-key SPACE_KEY [flags]

Examples


# List all properties for a space
acs2md space properties by-key DOCS
 
# JSON output
acs2md space properties by-key DOCS --format json
 
# Save to file
acs2md space properties by-key DOCS --format yaml --output props.yaml
 
# Limit results
acs2md space properties by-key DOCS --limit 10

Aliases

by-key can also be invoked as key or k.

Flags

Flag	Short	Default	Description
`--format`	`-f`	`table`	Output format: `table`, `json`, `yaml`
`--output`	`-o`	(stdout)	Output file path
`--limit`	`-l`	`25`	Number of results per page
`--cursor`	`-c`	(none)	Pagination cursor for the next page of results

Properties by ID


acs2md space properties by-id SPACE_ID [flags]

Lists properties for a space using its numeric ID instead of its key. Same flags as by-key.


acs2md space properties by-id 65539 --format json

Aliases

by-id can also be invoked as id.

Command aliases

The properties command can also be invoked as props or prop.


# These are equivalent
acs2md space properties by-key DOCS
acs2md space props by-key DOCS
acs2md space prop by-key DOCS

Use cases

Inventory and audit — discover what apps and integrations have attached data to your spaces.
Migration planning — identify custom properties that may need special handling during a migration.
Governance — verify that required metadata (e.g., classification labels, ownership tags) is present on spaces.

Space properties are distinct from page properties. They are set at the space level and are often used by Confluence apps to store configuration or state.