PATCH /categories/{category}

Update a Category

This endpoint allows you to update a Category. Have in mind that you cannot change a Category's type. E.g.: change a Category of type TYPE_OF_EQUIPMENT to SOFT_MAINTENANCE.

Changing the all_technical_skills field is restricted to admin operators; any other operator receives a 403 response.

Operation ID: updateCategory

lock This endpoint requires a Bearer token in the Authorization header.

Path Parameters

Name	Type	Description
`category` required path	string	The ID of the Category

Request Body

Content-Type: application/json

name string

Category name. Must be unique across the same "level".

Example: Ventilation

code string

Category code. Must be unique across the same "level".

Example: VENT

parent_id integer | null

Parent ID of Category

Example: 123

all_technical_skills boolean

Whether the category accepts operators with any technical skill. Only admin operators may change this field; any other operator receives a `403` response.

Example: 1

Responses

data object

Category model structure details

id string required read-only

ID of the Category

Example: 123

type string required read-only

Model type

category

Example: category

attributes object required

category_id integer read-only

ID of the Category

Example: 123

type string

The Category type. A "TYPE_OF_EQUIPMENT" Category is directly related to equipments (e.g. a fridge) and a Category "SOFT_MAINTENANCE" is related to Locations (E.g. hotel rooms).

SOFT_MAINTENANCE TYPE_OF_EQUIPMENT

Example: SOFT_MAINTENANCE

all_technical_skills boolean | null

Indicates if this category is associated to all technical skills.

Example: 1

code string

Code of the Category.

Example: VENT

entity_id integer

Entity ID of the Category.

Example: 123

full_code string | null read-only

Codes of the category's parents concatenated by dot with category code.

Example: XYZ.VENT

has_children boolean read-only

Whether the category has subitems or not.

Example: 1

is_real boolean | null

Whether the category is a folder (false) or "final" category (true).

Example: 1

name string

Name of the Category.

Example: Ventilation

parent_id integer | null

ID of the category parent.

Example: 123

relationships object

Available relationships of the Category.

categoryMeterings object

Category Meterings associated to the category.

characteristics object

Characteristics associated to the category.

entity object

Entity associated to the category.

files object

Files associated to the category.

maintenanceProcedures object

Maintenance Procedures associated to the category.

maintenancePolicies object

Maintenance Policies associated to the category.

problems object

Problems associated to the category.

technicalSkills object

Technical Skills associated to the category.

status string

error

error object

properties object

Only present when related to property validation error

dev_message string

Example: Property validation error. Check the "properties" section in the response.

http_code integer

400

message string

Example: Property validation error.

more_info string

status string

error

error object

http_code integer

401

message string

Example: Authentication token invalid.

more_info string

status string

error

error object

http_code integer

403

message string

Example: Action unauthorized

more_info string

status string

error

error object

http_code integer

404

message string

Example: Resource not found

more_info string | null

status string

error

error object

http_code integer

429

message string

Example: Too Many Requests.

more_info string

status string

error

error object

http_code integer

500

message string

Example: An error has occurred during the request.

more_info string

play_circle Try It

Environment

Authorization

Bearer

Path Parameters

category

Request Body

PATCH https://api.sandbox.infraspeak.com/v3/categories/{category}

curl -X PATCH \
  'https://api.sandbox.infraspeak.com/v3/categories/{category}' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_API_TOKEN' \
  -d '{
    "name": "Ventilation",
    "code": "VENT",
    "parent_id": 123,
    "all_technical_skills": true
}'

const response = await fetch('https://api.sandbox.infraspeak.com/v3/categories/{category}', {
  method: 'PATCH',
  headers: {
    'Accept': 'application/json',
    'Content-Type': 'application/json',
    'Authorization': 'Bearer YOUR_API_TOKEN',
  },
  body: JSON.stringify({
    "name": "Ventilation",
    "code": "VENT",
    "parent_id": 123,
    "all_technical_skills": true
}),
});

const data = await response.json();

$response = Http::withHeaders([
    'Accept' => 'application/json',
    'Content-Type' => 'application/json',
])->withToken('YOUR_API_TOKEN')
  ->patch('https://api.sandbox.infraspeak.com/v3/categories/{category}',
    array (
      'name' => 'Ventilation',
      'code' => 'VENT',
      'parent_id' => 123,
      'all_technical_skills' => true,
    )
  );

import requests

response = requests.patch(
    'https://api.sandbox.infraspeak.com/v3/categories/{category}',
    headers={
        'Accept': 'application/json',
        'Content-Type': 'application/json',
        'Authorization': 'Bearer YOUR_API_TOKEN',
    },
    json={
        {
            "name": "Ventilation",
            "code": "VENT",
            "parent_id": 123,
            "all_technical_skills": true
        }
    },
)

data = response.json()

data_object Example Response

200 OK

{
    "data": {
        "id": "123",
        "type": "category",
        "attributes": {
            "category_id": 123,
            "type": "SOFT_MAINTENANCE",
            "all_technical_skills": true,
            "code": "VENT",
            "entity_id": 123,
            "full_code": "XYZ.VENT",
            "has_children": true,
            "is_real": true,
            "name": "Ventilation",
            "parent_id": 123
        },
        "relationships": {
            "categoryMeterings": {},
            "characteristics": {},
            "entity": {},
            "files": {},
            "maintenanceProcedures": {},
            "maintenancePolicies": {},
            "problems": {},
            "technicalSkills": {}
        }
    }
}

400 Bad Request. Occurs when invalid parameters are provided or on data validation errors. For example, trying to create a resource without providing required fields. In this case, you can check the `properties` attribute on the response for more details.

{
    "status": "error",
    "error": {
        "properties": {},
        "dev_message": "Property validation error. Check the \"properties\" section in the response.",
        "http_code": 400,
        "message": "Property validation error.",
        "more_info": "string"
    }
}

401 Unauthorized. Authentication or permission error. E.g.: missing, incorrect or invalid Access Token.

{
    "status": "error",
    "error": {
        "http_code": 401,
        "message": "Authentication token invalid.",
        "more_info": "string"
    }
}

403 Forbidden. The action can not be fulfilled.

{
    "status": "error",
    "error": {
        "http_code": 403,
        "message": "Action unauthorized",
        "more_info": "string"
    }
}

404 Resource Not Found. Requests to resources that don't exist or are malformed.

{
    "status": "error",
    "error": {
        "http_code": 404,
        "message": "Resource not found",
        "more_info": "string"
    }
}

429 Too Many Requests. The client has sent too many requests in a given amount of time (check Throttling section).

{
    "status": "error",
    "error": {
        "http_code": 429,
        "message": "Too Many Requests.",
        "more_info": "string"
    }
}

500 Internal Server Error. Please, report us and try to provide as much information as possible, such as the endpoint, HTTP request headers and request body if applicable.

{
    "status": "error",
    "error": {
        "http_code": 500,
        "message": "An error has occurred during the request.",
        "more_info": "string"
    }
}