---
title: "REST API: Update Space"
type: "wiki"
space: "Axero Documentation"
author: "Anonymous User"
created: 2011-03-29T06:17:13Z
updated: 2026-09-28T01:21:31Z
tags: ["API"]
url: "https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/509/rest-api-update-space"
---

# REST API: Update Space

[Open API Guide](https://my.axerosolutions.com/spaces/5/axero-documentation/api-guide?id=509)
PUT/api/spaces/\{spaceid\}

Update a space. Send only the fields to change; the rest keep their current values. ResponseMessage is the string True when the space was saved and ResponseData is the SpaceID.

## Request

### Request Header
| Header | Required | Value | Description |
| :--- | :--- | :--- | :--- |
| `Authorization` | YES | `Bearer YOUR_TOKEN` | Bearer token for the authenticated user. [Learn how to create Bearer tokens](https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/108973/creating-bearer-tokens). |
| `Content-Type` | YES | `application/json` | Must be set to `application/json` |
### Required Parameters
| Parameter | Type | Required | Location | Description |
| :--- | :--- | :--- | :--- | :--- |
| `SpaceID` | Integer | YES | Path | Unique identifier for a particular space |
| `Space JSON` | String | YES | Body | The fields to change, as a JSON object \(a set of named fields and their values\). Each name must match exactly, including case: a name the space does not have, such as description in lowercase, answers 500. A value that cannot be converted sets a true or false field to false and a number field to 0. |
### Optional Parameters
| Parameter | Type | Required | Location | Description |
| :--- | :--- | :--- | :--- | :--- |
| `SpaceName` | String | NO | Body | New name for the space. The update does not check whether another space already uses the name. |
| `Description` | String | NO | Body | Summary text displayed on the space landing page, describing the space's purpose to members. A JSON list or another value that is not text is saved as its JSON text. |
| `EnableArticles` | Boolean | NO | Body | Set "articles" module on/off |
| `EnableBlogs` | Boolean | NO | Body | Set "blogs" module on/off |
| `EnableEvents` | Boolean | NO | Body | Set "events" module on/off |
| `EnableFiles` | Boolean | NO | Body | Set "files" module on/off |
| `EnableForums` | Boolean | NO | Body | Set "forums" module on/off |
| `EnableIssueTracker` | Boolean | NO | Body | Set "issues" module on/off |
| `EnablePhotos` | Boolean | NO | Body | Set "photos" module on/off |
| `EnableVideos` | Boolean | NO | Body | Set "videos" module on/off |
| `EnableWiki` | Boolean | NO | Body | Set "wiki" module on/off |
| `SpaceVisibility` | Integer | NO | Body | Visibility of the space. Accepted values:<br><br>Private = 0,<br>Public = 1,<br>Isolated = 3. A number outside these values is saved as sent, and a value that is not a number answers 500. |
| `IsFeatured` | Boolean | NO | Body | Make the space featured |
| `IsArticleWorkflowActive` | Boolean | NO | Body | Set "article" workflow on/off |
| `IsBlogWorkflowActive` | Boolean | NO | Body | Set "blog" workflow on/off |
| `IsEventWorkflowActive` | Boolean | NO | Body | Set "event" workflow on/off |
| `IsFileWorkflowActive` | Boolean | NO | Body | Set "file" workflow on/off |
| `IsForumWorkflowActive` | Boolean | NO | Body | Set "forum" workflow on/off |
| `IsPhotoWorkFlowActive` | Boolean | NO | Body | Set "photo" workflow on/off |
| `IsVideoWorkFlowActive` | Boolean | NO | Body | Set "video" workflow on/off |
| `IsWikiWorkflowActive` | Boolean | NO | Body | Set "wiki" workflow on/off |
| `MembershipType` | Integer | NO | Body | Specifies the space moderation. Accepted values are:<br><br>Unmoderated = 0,<br>Moderated = 1. A value that is not a number answers 500. |
| `ParentSpaceID` | Integer | NO | Body | ID of the space to move this space under; 0 makes it a top-level space. A value that is not a number also moves the space to the top level. |
| `StatusID` | Integer | NO | Body | Status of the space, an EntityStatus value: Published = 1, Declined = 3. A value that is not a number sets the status to 0 \(PendingWorkflow\). |
## Example

### Request Header

```
Authorization: Bearer YOUR_TOKEN
Content-Type: application/json
```

### Request URL

`https://your-site.com/api/spaces/187`

### Request Body

```
{
  "Description": "A space where members share updates and answer each other's questions."
}
```

### Success Response

```
{
  "IsError": false,
  "ResponseMessage": "True",
  "ResponseData": 493
}
```

### Error Response

```
{
  "Message": "The request is invalid."
}
```

## Error Handling

| Status Code | Likely Cause | Next Action |
| :--- | :--- | :--- |
| 400 Bad Request | spaceid in the path is not an integer. | Send a numeric SpaceID and a JSON object body. |
| 401 Unauthorized | Missing or invalid Bearer token. | Check token validity. [Learn how to create Bearer tokens →](https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/108973/creating-bearer-tokens) |
| 403 Forbidden | The caller cannot update spaces site-wide and is not an administrator of this space. | Confirm the user has the required roles for this action. |
| 500 Server Error | The body is missing or null, names a field the space does not have, gives SpaceVisibility or MembershipType a value that is not a number, or no space has that ID. | Check the body and the SpaceID, then retry later. |

## Rate Limits

While Axero does not enforce hard rate limits by default, we recommend the following best practices to ensure optimal performance:

- **Sustained Request Rate:** Do not exceed 5 API calls per second
- **Sequential Processing:** Wait for each request to complete before sending the next in automated workflows
- **Concurrent Connections:** If parallel processing is required, limit to 3 or fewer simultaneous requests
- **Response Timeout:** Ensure API responses complete within 15 seconds during testing

Axero may implement temporary rate restrictions if excessive API usage affects overall site performance. For high-volume integrations, contact Axero to discuss your requirements.
