Loading ...

REST API: Create Case Project Categories | Axero Documentation

Home » axero documentation » Wiki » Documentation » REST API Overview » REST API: Content » REST API: Cases » REST API: Create Case Project Categories
Axero Documentation  Wiki
Public Space
Activity Stream Content
Version 22

REST API: Create Case Project Categories

0 
 /5
0 (0votes)
Open API Guide
POST/api/cases/projects/{ProjectID}/categories

Create a list of categories for a particular case project

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
ProjectIDIntegerYESPathUnique identifier for a particular case project
CategoryNameStringYESBodyDisplay name for the project category used to classify cases within a project.

Optional Parameters

ParameterTypeRequiredLocationDescription
SpaceIDIntegerNOBodySpace ID if the category belongs to a space. If not provided, the category will be created for the top level community.

Example

Request Header

Authorization: Bearer YOUR_TOKEN
Content-Type: application/json

Request URL

https://your-site.com/api/cases/projects/484/categories

Request Body

{
  "CategoryName": "Bug Reports"
}

Success Response

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

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. (projectID, requestBody)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 case project category was not found.Verify the caseID 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