Hi.

It would be much easier for developing integrations if Zabbix API methods (specially the host.get) could provide a easier way to search for new content only (using some sort of 'last_modified_date' field) and pagination (like 'offset' or 'start_from') to avoid overloading the server and the receiver with same data.

Use Case 1: Zabbix server has 15.000 hosts registered and an external system needs to retrieve them all, but in small parts (e.g. 15 parts of 1.000 hosts, or 30 parts of 500 hosts), to not overload Zabbix nor the external system.

Using pagination, an external system can request for NN items in every iteration, and keep interacting until the all the items are received.

Use Case 2: An external system needs to retrieve only changed hosts in the last NN minutes (e.g. 60 minutes). Today, the external system needs to retrieve all hosts every time and keep retrieved data for future reference. At every iteration, system needs to compare current output with previous stored output to define if a host was changed.