I am using i-doit OPEN version 1.18.2 with API add-on version 1.12.3.
I would like to update the API add-on to version 1.14.1 to solve an specific bug that is giving us trouble.

Is it possible?
I have been unable to find the add-on available for download.
I have read in https://i-doit.org/ that the API is no longer available for i-doit open since version 29.
However, I would like to maintain my current i-doit version.

Hello,

I have discovered I can enter logbook entries manually or using the API. However, I have not found any way to modify manually/API created logbook entries.

Is it possible?

Hello @Eduardo-Casarero,

You should try using the method cmdb.category.read for category "C__CATS__PERSON_ASSIGNED_GROUPS" using the user id.

{
    "version": "2.0",
    "method": "cmdb.category.read",
    "params": {
        "objID": 158,
        "category": "C__CATS__PERSON_ASSIGNED_GROUPS",
        "apikey": "XXX"
    },
    "id": 1
}

Hello,

I have noticed that IPv4 address is not validated through the API in the same way it is validated in the web.

When created in the web, it is not acceptable to include an address that is not the IP range of the net or that already exits. However, there are no issues in doing so using the API.

I have been able to reproduce this both on i-doit demo and on my i-doit 1.18.2 OPEN installation.

Is there a way to enforce IPv4 address validation through the API?

Thank @Michael-Overkamp!

I confirm that the hotfix solves the issue.

I am currently using i-doit 1.18.2 OPEN and API 1.12.3.
In this setup, there are some API calls that fail and that used to work in my previous i-doit version. They are still working in the i-doit demo.

The API response includes the error: "The provided property is virtual and can not be updated via API. Please provide a valid definition."
I have not been able to find anything in the changelog that suggests why this may happen. I have not found any reference to virtual properties in the Knowledge Base either.

The API call that fails are the following.

• Creating 'C__CATS__FILE_VERSIONS' including 'file_content' property

{
    "version": "2.0",
    "method": "cmdb.category.save",
    "params": {
        "object": 3628,
        "category": "C__CATS__FILE_VERSIONS",
        "apikey": "XXXXX",
        "language": "en",
        "data": {
                "file_title": "file.txt",
                "file_physical": "file.txt",
                "file_content":"VGhpcyBpcyBhIHRlc3QgZmlsZS4NClRoaXMgaXMgYSB0ZXN0IGZpbGUuDQpUaGlzIGlzIGEgdGVzdCBmaWxlLg0KVGhpcyBpcyBhIHRlc3QgZmlsZS4NClRoaXMgaXMgYSB0ZXN0IGZpbGUuDQpUaGlzIGlzIGEgdGVzdCBmaWxlLg=="
            }
    },
    "id": 1
}

Error:

{
    "id": 1,
    "jsonrpc": "2.0",
    "error": {
        "code": -32603,
        "message": "Internal error: There was an validation error",
        "data": {
            "file_content": "(The provided property is virtual and can not be updated via API. Please provide a valid definition.) "
        }
    }
}

• Creating C__CATG__NETWORK_PORT including 'addresses' property

{
  "version": "2.0",
  "method": "cmdb.category.save",
  "params": {
    "apikey": "XXXXX",
    "language": "en",
    "object": 1334,
    "category": "C__CATG__NETWORK_PORT",
    "data": {
      "title": "eth0",
      "port_type": "Ethernet",
      "addresses": 209
    }
  },
    "id": 1
}

Error:

{
    "id": 1,
    "jsonrpc": "2.0",
    "error": {
        "code": -32603,
        "message": "Internal error: There was an validation error",
        "data": {
            "addresses": "(The provided property is virtual and can not be updated via API. Please provide a valid definition.) "
        }
    }
}

Hello,

I'm exploring different ways of exporting and importing data from i-doit.
I've seen the XML import option. Is it also possible to export data as XML?

In this topic, it is explained how to manage tags using the API. The limitations in the use of tags I mention in my previous post do not exist.

However, I am still wondering about the consequences of using tags vs object groups.

Thanks @michael-overkamp!

I had not undestood that multiselect is a Dialog+, I thought it was a different kind of attribute.

Thanks @michael-overkamp!
It works fine.