The API token used for authenticating the request. This must be passed as a header parameter. To generate an API token, go to Settings > Knowledge base portal > API tokens. This token must correspond to a valid workspace and permission level.
The ID of the category
Language code of the category
This is an basic example for unpublish category. ProjectVersionId, UserId and VersionNumber are mandatory.
{
"user_id": "f11efc6f-e968-4e95-82eb-85ad61559de8",
"project_version_id": "46f48bc7-760f-4b07-b2d2-fce4aa8ba234",
"version_number": 1,
"unpublish_message": "Successfully unpublished"
}The ID of the team account who is responsible for the unpublish
The project version ID where the article exists.
The version number of the category
Unublish message for the category
This is an basic example for unpublish category. ProjectVersionId, UserId and VersionNumber are mandatory.
{
"user_id": "f11efc6f-e968-4e95-82eb-85ad61559de8",
"project_version_id": "46f48bc7-760f-4b07-b2d2-fce4aa8ba234",
"version_number": 1,
"unpublish_message": "Successfully unpublished"
}The ID of the team account who is responsible for the unpublish
The project version ID where the article exists.
The version number of the category
Unublish message for the category
This is an basic example for unpublish category. ProjectVersionId, UserId and VersionNumber are mandatory.
{
"user_id": "f11efc6f-e968-4e95-82eb-85ad61559de8",
"project_version_id": "46f48bc7-760f-4b07-b2d2-fce4aa8ba234",
"version_number": 1,
"unpublish_message": "Successfully unpublished"
}The ID of the team account who is responsible for the unpublish
The project version ID where the article exists.
The version number of the category
Unublish message for the category
This is an basic example for unpublish category. ProjectVersionId, UserId and VersionNumber are mandatory.
{
"user_id": "f11efc6f-e968-4e95-82eb-85ad61559de8",
"project_version_id": "46f48bc7-760f-4b07-b2d2-fce4aa8ba234",
"version_number": 1,
"unpublish_message": "Successfully unpublished"
}The ID of the team account who is responsible for the unpublish
The project version ID where the article exists.
The version number of the category
Unublish message for the category
Success
Unublishing a page category with CategoryId, project_veriond_id, langCode, user_id, version_number, and unpublish_message.
{
"extension_data": null,
"success": true,
"errors": [],
"warnings": [],
"information": []
}bulk category response data
The ID of the category
True - Category is published
False - Category is not published
Description of the action performed
Extension data for customer API response
Indicates the status of the API response. A value of true signifies that the request was successfully processed, while false indicates a failure or error occurred.
A list of errors encountered during the API request. Each error object provides details about the problem, including an error code and a message explaining the issue. This field is populated when the request fails or encounters issues.
This is the Extension data object
A technical trace showing where the error occurred within the system. Intended for backend debugging.
A clear message explaining what caused the error. This helps quickly understand what went wrong.
A short, predefined code that identifies the type of error. Useful for logging the error or raising a support request.
Any structured metadata for the error object.
A list of warnings generated during the API request. These are non-critical issues or recommendations that might affect the request but won't stop it from processing. Each warning object provides a message to inform the user of potential problems.
Extension Data for customer Api warning
A plain message that describes the warning and helps understand what should be reviewed.
A short, predefined code that uniquely identifies the warning type.
Contains additional non-critical information relevant to the request or response. This field provides extra details that might assist in understanding the context of the API response but is not essential for processing.
Extension data for customer Api response information
A plain message offering helpful context about the response, such as confirmation of fallback logic or skipped operations.
Bad Request
kindly verify the CategoryId and perform the task again.
{
"extension_data": null,
"success": false,
"errors": [
{
"extension_data": null,
"stack_trace": null,
"description": "Category not found.",
"error_code": "400",
"custom_data": null
}
],
"warnings": [],
"information": []
}kindly verify the version_number and perform the task again.
{
"extension_data": null,
"success": false,
"errors": [
{
"extension_data": null,
"stack_trace": null,
"description": "The field VersionNumber must be between 1 and 32767.",
"error_code": "400",
"custom_data": null
}
],
"warnings": [],
"information": []
}Kindly verify the user_id nad perform the task again.
{
"extension_data": null,
"success": false,
"errors": [
{
"extension_data": null,
"stack_trace": null,
"description": "The UserId field is required.",
"error_code": "400",
"custom_data": null
}
],
"warnings": [],
"information": []
}Extension data for customer API response
Indicates the status of the API response. A value of true signifies that the request was successfully processed, while false indicates a failure or error occurred.
A list of errors encountered during the API request. Each error object provides details about the problem, including an error code and a message explaining the issue. This field is populated when the request fails or encounters issues.
This is the Extension data object
A technical trace showing where the error occurred within the system. Intended for backend debugging.
A clear message explaining what caused the error. This helps quickly understand what went wrong.
A short, predefined code that identifies the type of error. Useful for logging the error or raising a support request.
Any structured metadata for the error object.
A list of warnings generated during the API request. These are non-critical issues or recommendations that might affect the request but won't stop it from processing. Each warning object provides a message to inform the user of potential problems.
Extension Data for customer Api warning
A plain message that describes the warning and helps understand what should be reviewed.
A short, predefined code that uniquely identifies the warning type.
Contains additional non-critical information relevant to the request or response. This field provides extra details that might assist in understanding the context of the API response but is not essential for processing.
Extension data for customer Api response information
A plain message offering helpful context about the response, such as confirmation of fallback logic or skipped operations.