Loading ...

REST API: Update Role | Axero Documentation

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

REST API: Update Role

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

Supports the synchronization and modification of update role properties via the API.

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.

Example

Request Header

Authorization: Bearer YOUR_TOKEN
Content-Type: application/json

Request URL

https://your-site.com/api/roles/132

Request Body

{
  "RoleName": "Quality Analyst",
  "Description": "A software quality analyst is responsible for applying the principles and practices of software quality assurance throughout the software development life cycle."
}

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 RequestOne or more required fields are missing or invalid. (roleID, source)Verify the request payload against the required parameters.
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.
404 Not FoundThe specified role was not found.Verify the roleID is correct.
500 Server ErrorInternal failure.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