the units are available through a separate call to e.g. http://localhost:7080/rest/1/resource/10001/schedules.html or more specific http://localhost:7080/rest/1/metric/schedule/10018.html
The idea here is that a client grabs the schedule information once and then repeatedly the metrics, so the static information like units could stay in the more static part.
We need a better way of exposing the api documentation, but for a start you can go to http://localhost:7080/rest/ and browse the starting html pages there, which guide
you around (most parts of) the interface. If you then replace the .html suffix with .json (or leave it out and send an accept type of application/json you should be good
to use it in your application. Unfortunately this does not yet tell about the possible parameters and default values.