no foreign keys in database?

[Alexei]

I see that the API is mostly needed for management of ZABBIX configuration. It shouldn't be difficult to implement.

[r3dn3ck]

From my perspective that's purely the need. I don't know about anyone else but I can't imagine a whole lot more uses.

[teferi]

add/change/remove hosts
add/change/remove host profile data
add/change/remove host group assignment
add/change/remove host template assignment
Enable/Disable monitoring on HOST(x)
Enable/Disable monitoring on template members (all hosts in a template affected)
Enable/Disable monitoring on group members (all hosts in a group affected)

I'd add the following:
add/change/remove items to host(without templates. It's usefull in some situations)
add/change/remove graphs
add/change/remove screens


Well I think wouldn't lie if I say that most of these functions can be found in the php frontend. =))

[r3dn3ck]

If there's going to be an API built for any of it then might as well do the other basics.

[xs-]

@alexei
I've been looking at the zabbix code with a colleague to see how much time it would take and how complex it would be.
Basically, all real functionality is already available via php functions in the webcode. The only real decision to be made is what kind of interface would the API have, cmdline / webbased (i.e. soap), XML or something else, etc, etc.
We've been looking at the API (xml) spec used by mediawiki, perhaps this is a good example.

Purposes for this API (imho) are purely administrative yes; you don't want this level of 'open' management available outside of your control.
For example to hook Zabbix to a CMDB for automatic host/hostgroup/users/usergroup management. Another example would be to write a script to rotate phonenumers of standby services. The applications are endless ofcourse, but purely backend related.

[nelsonab]

Let's move the discussion here:

http://www.zabbix.com/forum/showthread.php?p=36034