Onedata API Reference

REST API references for Onezone, Oneprovider, and Onepanel.

Version:

Onezone REST API Oneprovider REST API Onepanel REST API

Version:

Create new space (admin)

POST /spaces

Creates a new space.

This operation requires oz_spaces_create admin privilege.

Equivalent endpoints for regular users:

Create a new space for the current user
Create a new space for given group

Example cURL requests

Create a new space

curl -u username:password -H "Content-type: application/json" \
-X POST -d '{ "name" : "new_space" }' \
https://$ZONE_HOST/api/v3/onezone/spaces

Request body

application/json

Space creation data.

Property	Type & Description
name required string The name of the new space.
description string (SpaceDescription) Space description in markdown (.md) format.
organizationName string (SpaceOrganizationName) Name of the organization responsible for space management.
tags array of strings A list of short keywords or phrases that helps to understand the purpose of a space. Available space tags can be retrieved from the configuration endpoint.
advertisedInMarketplace boolean (SpaceAdvertisedInMarketplace) Specifies whether the space should be publicly advertised in the Space Marketplace.
marketplaceContactEmail string (SpaceMarketplaceContactEmail) Email address that will be used for notifying the person responsible for space management in the Marketplace about new membership requests. This field is visible only to space members with both `space_view` and `space_manage_in_marketplace` privileges, otherwise an empty string is returned. Similarly, it can be modified only by users with the `space_manage_in_marketplace` privilege.

Request Examples

Shell

onezone-rest-cli createSpace name=="Space 1"

Responses

application/json

201

URI of the created space in the form https://$ZONE_HOST/api/onezone/v3/spaces/{id} is returned in the response Location header.

400

Invalid request.

Property

Type & 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.

Property

Type & 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.

Property

Type & 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.

Property

Type & 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.

Property

Type & 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."
  }
}