Space Tool Fields


To fetch metadata of Space Tool object send a GET request to:

https://api.assembla.com/v1/meta/space_tools.(json|xml)

Example. Request JSON with cURL utility:

curl -H "Authorization: Bearer _token" https://api.assembla.com/v1/meta/space_tools.json

Example. Request XML with cURL utility:

curl -H "Authorization: Bearer _token" https://api.assembla.com/v1/meta/space_tools.xml

Table below is the list of fields contained in the response, this list will be properly formatted to JSON or XML as requested.

Fields

Param Data type Access Description
id string read Space tool identifier
space_id string read ID of space where tool is installed on
active boolean read Active flag
url string read If a forked repo tool or a repo tool with modified url, this is the url to repository
number integer read If space has many instances of one tool, numeration is triggered on identic tools.
watcher_permissions integer read/write Permissions for watchers, possible values are:
  • 1, watchers have access to view space tool
  • 2, watchers have edit permissions for space tool
  • 3, watchers have all permissions for space space
team_permissions integer read/write Permissions for space members, possible values are:
  • 1, space members have access to view space tool
  • 2, space members have edit permissions for space tool
  • 3, space members have all permissions for space space
public_permissions integer read/write permissions for public visitors(if space is public), possible values are:
  • 1, space members have access to view space tool
  • 2, space members have edit permissions for space tool
created_at datetime read Date and time when space tool was created
tool_id integer read/write(on tool creation) ID of tool, available values are:
  • 9, Milestones
  • 10, StandUp
  • 12, Source/SVN
  • 13, Tickets
  • 14, Time
  • 17, Source/Hg
  • 18, Files
  • 20, External Subversion
  • 21, Messages
  • 22, Github
  • 23, Wiki
  • 24, Source/P4
  • 111, Twitter
  • 112, Webhook
  • 128, Source/Git
  • 116, FTP
  • 117, Custom tab
  • 300, Support
type string read The string value of tool_id after tool is created
parent_id string read ID of parent tool if it was forked
menu_name string read Concatenated pretty formatted name and tool number, you can see these values in space tools navigation tabs.
name string read Strict name of tool plus tool number, can be used as tool identifier also, if not name is available for the tool this field will present the ID.

Validations

Field Validator Description
space_id presence validator Space id should be present.
tool_id uniqueness validator Only one instance for some tools is allowed per space.