ver. 1926 (dbed1d0)
Retrieve information on multiple log entries
This method works like the services/logs/entry method, but works with multiple log entries (instead of only one).
Pipe-separated list of UUIDs. These represent the log entries you are interested in. No more than 500 codes are allowed. Unlike in the "entry" method, this CAN be an empty string (it will result in an empty, but valid, response).
Default value: date|user|type|comment
Same as in the services/logs/entry method. Pipe-separated list of field names which you are interested in. See services/logs/entry method for a list of available values.
Default value: uuid|username|profile_urlSame as in the services/logs/entry method. Pipe-separated list of user fields to include in the user field. For valid field names, see the services/users/user method.
|format||optional||Standard common formatting argument.|
|callback||optional||Standard common formatting argument.|
|Plus required consumer_key argument, assigned for your application.|
A dictionary. UUIDs you provide will be mapped to dictionary keys, and each value will be a dictionary of fields you have selected.
Value of null means that the given UUID haven't been found. (This behavior is different than in the services/logs/entry method, which responds with an HTTP 400 error in such case.)