Menu

Reading Workday and Rippling job boards without a scraper (and the pagination trap)
📰

Reading Workday and Rippling job boards without a scraper (and the pagination trap)

DEV Community: api·Martin Pisacreta·about 10 hours ago
#VioYCORM
#devtoapi#devto#dev#jobs#board
Reading 0:00
15s threshold

I added Workday and Rippling to my jobs monitor by reading their job-list responses directly. The useful discovery was not just the endpoints. It was a pagination detail that could make a working Workday integration stop early while reporting success. My saved second page contained twenty jobs and a total of zero. Treating that zero as the end of the board would have discarded valid results.

Everything below is what I observed on real boards while building that integration. Neither endpoint is a documented public API, so treat this as a starting point: it can change, and another employer's board may behave differently.

Workday: start with the public board URL

My Workday example starts with NVIDIA's public board address. Its hostname supplies two pieces: nvidia is the tenant and wd5 is the cluster. The path supplies the site, NVIDIAExternalCareerSite .…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.