Vote for Zabbix API

[tekknokrat]

Thanks for participating in the voting! It was decided to implement JSON-RPC!

The work is already in progress.Stay tuned!

good news.
Will that be json-rpc over http? I would prefer it that way because its more flexible (like prev. poster stated). E.g. authentication would be easier to implement, better usage from within a webframework, ajax all that would be possible

[Aly]

Yes, it will be over http.

[Kaspgagsdow]

Vote for Zabbix API

Now that vbulletin 4.0 has a cross content search system, I would like to address the above question again.

Im hoping for a blog post or an explanation:

How can developers accomplished search engine integration for their addons?

[globifrosch]

examples

are there any example scripts how to use the api?

[Tenzer]

The API is not made yet...

[globifrosch]

The API is not made yet...

if I have a look at the source code, there is api_jsonrpc.php and a folder api/* with files in it. i think at least partial code is there.

i like to test it.

[nelsonab]

I've been reading through the documentation too, it's a little scant on comments, but it's at least a start. :-)

[nelsonab]

I've been working with the Zabbix API a little and it definately has a lot of promise. Yes the transport mechanism is JSON over HTTP. I've used both a C# and Ruby library and I've found the Ruby library to be quite stable and works very well.

I hope to have more soon. :-)

[alj]

Was to late because Vote is closed.
Anyway my Vote for JSON-RPC. 2nd choice would have been REST.

Why:
- It is pretty simple to use
- JSON and JSON-RPC are more and more supported and used
- XML has a larger overhead
- Given, that the API is just about exchanging data without any presentation, JSON can be used easily by any client/frontend app
- Looking especially to WEB 2.0 application design, JSON seems to be the winner simply because of Javascript on the clientside

XML seems like getting unpopular theese days because it is resource hog which is probably true.
Most of modern software uses REST or JSON as far as i can see.
Even databases start to use REST interface (such as couchdb).

[Jason]

It'd be nice if there was an API section of the wiki where api scripts could be posted as I think it'd be a nice resource and a help to people to get started with their own API's.

[nelsonab]

It'd be nice if there was an API section of the wiki where api scripts could be posted as I think it'd be a nice resource and a help to people to get started with their own API's.

I could see that being potentially useful too.

[richlv]

It'd be nice if there was an API section of the wiki where api scripts could be posted as I think it'd be a nice resource and a help to people to get started with their own API's.

well, it's... a wiki... afterall

[Jason]

I think a section for API contributions needs to come off the root document which we don't have access to by default... Someone with access would need to create that and sort the rights before can do any more...

[nelsonab]

Can we unsticky this thread?

[Alexei]

Can we unsticky this thread?

Sure, I just did it!