ver. 1926 (dbed1d0)
Get information on available logging features
This method tells which features are available when your user will submit or edit a log entry.
Using this method is always optional. You never need to know about differences between OKAPI installations or logging preconditions. If a logging feature is not avaible, OKAPI will accept the request and return a user-friendly explanation. But you may use this method to improve usability of your app, e.g. by disabling nonfunctional options.
The code of the geocache to be logged. Available features for services/logs/submit will be returned. Either this or the log_uuid argument must be supplied.
The UUID of the log entry to be edited. Available features for services/logs/edit will be returned. Either this or the cache_code argument must be supplied.
The type of log entry the user wants to submit; one of the identifiers returned as submittable_logtypes by an earlier call to this method. If given, all the can_ fields will reflect the capabilities for this type of log. See the services/logs/entry method for more information on log types.
|format||optional||Standard common formatting argument.|
|callback||optional||Standard common formatting argument.|
|Plus required standard OAuth Consumer signing arguments: oauth_consumer_key, oauth_nonce, oauth_timestamp, oauth_signature, oauth_signature_method, oauth_version. Plus required oauth_token for Token authorization.|
A dictionary of the following structure:
The can_rate and can_..._maintenance fields currently are always false if a log UUID is supplied. OKAPI so far does not implement editing those log properties.