Onedata API Reference

REST API references for Onezone, Oneprovider, and Onepanel.

List space owners

GET /spaces/{id}/owners

Returns the list of owners of a specific space.

Space owners are members (users) of the space that have absolute power regarding the space API and files (analogical to "root", but in the scope of one space). Being an owner means that user privileges are essentially ignored and all API operations are allowed.

This operation requires any of the following authentication:

  • as user who has space_view privilege in the space ({id}),
  • as provider that supports the space ({id}),
  • as user who has oz_spaces_view admin privilege.

Example cURL requests

Get space owners

curl -u username:password -X GET \
https://$HOST/api/v3/onezone/spaces/$SPACE_ID/owners

{
  "users": [
    "a5b469a2b0516b662a49da74d6d7d7bc"
  ]
}

Path parameters

Parameter Type & Description
id required
string

Space Id.

Request Examples

Shell
onezone-rest-cli listSpaceOwners id=b752ceafabb662b4e5728b2ded25cdd1

Responses

application/json
200

The list of all user Ids that are owners of the space.

PropertyType & Description
users
array of strings

The list of user Ids.

Example

application/json
{
  "users": [
    "1d24c36707d99197c6cd995810a43aca",
    "6825604b0eb6a47b8b7a04b6369eb24d"
  ]
}
400

Invalid request.

PropertyType & Description
error
object

Object describing an error.

id required
string

String identifying the error type. Does not change between error instances.

description required
string

Human readable error description. May contain information specific to given error instance.

details
object

Details about the error instance. The object schema is specific to each error type.

Example

application/json
{
  "error": {
    "id": "badValueString",
    "details": {
      "key": "name"
    },
    "description": "Bad value: provided \"name\" must be a string."
  }
}
401

Authentication error.

PropertyType & Description
error
object

Object describing an error.

id required
string

String identifying the error type. Does not change between error instances.

description required
string

Human readable error description. May contain information specific to given error instance.

details
object

Details about the error instance. The object schema is specific to each error type.

Example

application/json
{
  "error": {
    "id": "badValueString",
    "details": {
      "key": "name"
    },
    "description": "Bad value: provided \"name\" must be a string."
  }
}
403

Authorization error.

PropertyType & Description
error
object

Object describing an error.

id required
string

String identifying the error type. Does not change between error instances.

description required
string

Human readable error description. May contain information specific to given error instance.

details
object

Details about the error instance. The object schema is specific to each error type.

Example

application/json
{
  "error": {
    "id": "badValueString",
    "details": {
      "key": "name"
    },
    "description": "Bad value: provided \"name\" must be a string."
  }
}
404

Resource not found.

PropertyType & Description
error
object

Object describing an error.

id required
string

String identifying the error type. Does not change between error instances.

description required
string

Human readable error description. May contain information specific to given error instance.

details
object

Details about the error instance. The object schema is specific to each error type.

Example

application/json
{
  "error": {
    "id": "badValueString",
    "details": {
      "key": "name"
    },
    "description": "Bad value: provided \"name\" must be a string."
  }
}
500

Internal server Error.

PropertyType & Description
error
object

Object describing an error.

id required
string

String identifying the error type. Does not change between error instances.

description required
string

Human readable error description. May contain information specific to given error instance.

details
object

Details about the error instance. The object schema is specific to each error type.

Example

application/json
{
  "error": {
    "id": "badValueString",
    "details": {
      "key": "name"
    },
    "description": "Bad value: provided \"name\" must be a string."
  }
}