---
title: "Update space by Id"
method: PUT
path: "/1.0/spaces/{spaceId}"
tags: ["Spaces"]
---

# Update space by Id

`PUT /1.0/spaces/{spaceId}`

## Path parameters

- `spaceId` integer, required

## Request body

- SpacePublicUpdateAPIRequestEntity
  - `spaceName` string — The name of the space.

## Response `200`

The requested action was successfully executed.

- SpacePublicResponseEntity
  - `spaceId` integer — The space's unique, system-generated identifier, which can be used to identify the space globally.
  - `spaceName` string — The name of the space.
  - `project` ProjectPublicAPISpaceResponseEntity — The `project` where the `space` exists.
    - `projectId` integer — The unique, system-generated identifier of the project associated with space.
    - `projectName` string — The name of the project associated with the space.
  - `createdAt` integer — The timestamp when the space was created. The referenced time will be in epoch millis.
  - `createdBy` SpaceCreatedByUserPublicAPI — The team member who created the space.
    - `emailId` string — The team members email identifier.
    - `userId` integer — The unique identifier for the user.
    - `firstName` string — The first name of the user.
    - `lastName` string — The last name of the user.
  - `updatedAt` integer — The timestamp when the space was last updated.
  - `updatedBy` SpaceUpdatedByUserPublicAPI — The team member who updated the project
    - `emailId` string — The team members email identifier.
    - `userId` integer — The unique identifier for the user.
    - `firstName` string — The first name of the user.
    - `lastName` string — The last name of the user.
  - `private` boolean — Describes the privacy of the space i.e. if it is private or shared.

## Other responses

- `400` — This error typically happens when the request payload contains an error. If you want to make sure that the request's parameters are named correctly and are the right data types, you can examine the request's syntax.
- `401` — You see this error when trying to access this resource without being authenticated. Check the API request header to make sure it is not empty and has a valid api-key that you acquired from the Rocketlane API Settings tab.
- `404` — If we were unable to locate the resource you were looking for or the proper API endpoint you were looking for, this error would show up.

---

[API](https://skmtc.net/rocketlane/apis/rocketlane-api.md) · [All operations](https://skmtc.net/rocketlane/apis/rocketlane-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/rocketlane/rocketlane-api/versions/1e8ba619e741/schema)