member badge
Shelton Wirth
Description of painpoint:
  • Our Real Time Analysts approve time off requests, but we cannot audit who approved which requests via the API. This blocks our ability to build data-driven approval workflows and eventual automation.
  • API limitation = the event_change object does not include a modified_by field, despite time off approvals creating event changes.
  • No relationship exists between activity_id (from /v0/activities) and time_off_request_id (from /v0/time_off/requests). When a time off request is approved and creates activities, we cannot programmatically link them. The Fivetran Assembled connector (https://fivetran.com/connector-erd/assembled) exposes these tables separately with no join key.
Requested changes:
  • Add modified_by_id field to event_change object (similar to existing pattern in other endpoints)
  • Add time_off_request_id field to activity object OR activity_id field to time_off_request object
  • Consider adding POST endpoints for approving/denying time off requests programmatically