Loading ...

REST API: Update Space Role | Axero Documentation

Home » axero documentation » Wiki » Documentation » REST API Overview » REST API: Spaces » REST API: Space Roles » REST API: Update Space Role
Axero Documentation  Wiki
Public Space
Activity Stream Content
Version 37

REST API: Update Space Role

0 
 /5
0 (0votes)
Open API Guide
PUT/api/spaces/{SpaceID}/roles/{RoleID}

Update a space role's name or description. ResponseData is true when the role was saved.

Request

Request Header

HeaderRequiredValueDescription
AuthorizationYESBearer YOUR_TOKENBearer token for the authenticated user. Learn how to create Bearer tokens.
Content-TypeYESapplication/jsonMust be set to application/json

Required Parameters

ParameterTypeRequiredLocationDescription
RoleIDIntegerYESPathUnique identifier for a particular role
Role JSONStringYESBodyThis is JSON that represents a role object that you're updating. This should be of the format seen below in the sample given.

Optional Parameters

ParameterTypeRequiredLocationDescription
RoleNameStringNOBodyDisplay name for the role. Must be unique within its scope (site-level or space-level).
DescriptionStringNOBodyHuman-readable description explaining what permissions or access this role grants.
SpaceIDIntegerYESPathUnique identifier of the space the role belongs to. Part of the route only: the role is looked up by RoleID.

Example

Request Header

Authorization: Bearer YOUR_TOKEN
Content-Type: application/json

Request URL

https://your-site.com/api/spaces/23/roles/780

Request Body

{
  "RoleName": "System Analyst",
  "Description": "A systems analyst uses computers and related systems to design new IT solutions, modify, enhance or adapt existing systems and integrate new features."
}

Success Response

{
  "IsError": false,
  "ResponseMessage": "",
  "ResponseData": true
}

Error Response

{
  "IsError": true,
  "ResponseMessage": "Required parameter is missing or invalid.",
  "ResponseData": null
}

Error Handling

Status CodeLikely CauseNext Action
400 Bad RequestSpaceID or RoleID in the path is not an integer, or the body is not a JSON object.Send numeric IDs and a JSON object body.
401 UnauthorizedMissing or invalid Bearer token.Check token validity. Learn how to create Bearer tokens →
403 ForbiddenUser does not have sufficient permissions.Confirm the user has the required roles for this action.
500 Server ErrorNo role has that RoleID (the endpoint merges into the result without checking), or another internal failure.Check the RoleID, 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.

Wiki Index

Pages