A callback is a function provided by the consumer of an API that the API can then turn around and invoke (calling you back). If I setup a Dr.’s appointment, I can give them my phone number, so they can call me the day before to confirm the appointment. A callback is like that, except instead of just being a phone number, it can be arbitrary instructions like “send me an email at this address, and also call my secretary and have her put it in my calendar.
Callbacks are often used in situations where an action is asynchronous. If you need to call a function, and immediately continue working, you can’t sit there wait for its return value to let you know what happened, so you provide a callback. When the function is done completely its asynchronous work it will then invoke your callback with some predetermined arguments (usually some you supply, and some about the status and result of the asynchronous action you requested).
If the Dr. is out of the office, or they are still working on the schedule, rather than having me wait on hold until he gets back, which could be several hours, we hang up, and once the appointment has been scheduled, they call me.
In this specific case, the documented method will compute the result, put it together with any callbackargs specified, and call callback, passing it those values as the arguments.