[ZBX-1100] API should have a call to query version information Created: 2009 Oct 17  Updated: 2017 May 30  Resolved: 2009 Oct 30

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: API (A)
Affects Version/s: 1.9.0 (alpha)
Fix Version/s: 1.9.0 (alpha)

Type: Problem report Priority: Critical
Reporter: nelsonab Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Adding this ticket to Bugs and Issues as this should be implemented now and not in a future version.

There needs to be an API call to query the version of the server. The call could return information like the version of the API and possibly the Zabbix server itself as it is possible that the API may not track the Zabbix server as quickly or closely. However it is implemented is not important to me as long as it is documented well and adhered to.

This function will be of tantamount importance to authors of API stacks as it would then be possible for the author of the API stack to check compatibility with the API available before making a call. The check version call should also not require any authentication,



 Comments   
Comment by richlv [ 2009 Oct 18 ]

i'm not completely sure about no auth thing, might be considered a security thing. maybe api version w/o auth, zabbix frontend version with auth ?

Comment by nelsonab [ 2009 Oct 18 ]

I can see not giving all information without login, however it is very important to at least give version number or some other rudimentary information about the API without requiring a login. In time I can envision something like this happening.

1) Connect to API and determine API verison
2) Login to API
3) Check API capabilities
4) Setup local environment (may not always happen, but would mostly happen with CLI tool for example)
5) Perform actions.

Comment by Alexey Fukalov [ 2009 Oct 30 ]

added method apiinfo.version to get api version, available without authentication.
trunk 8142.

Comment by richlv [ 2009 Dec 16 ]

closing resolved issues

Generated at Thu May 22 06:43:56 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.