Incomplete Variable Set in API Endpoints

There’s a number of places where the API differs from GUI on data points available for reference, for example:

/api/v1/events/{id} doesn’t report the adult and girl coordinators, permission, medical, and tour plan boles, permission slip due date, attachments, attendance uniform status, or RSVP comments.

/api/v1/user_achievements doesn’t report the awarded_on date

/api/v1/users/{id} doesn’t report the notes field and some the driver and registration related fields

There may be others in endpoints that I haven’t try to use.

Are these omissions considered bugs, i.e. is it the intent that API exposes the same data as the GUI? Or are there deliberate decisions (perhaps related to the underlying DB design) that drive these limitations?

1 Like