For Developers

Connect your hiring systems
to HR Worker.

Ten calls. Eight reads to see what is happening at your stores, and two writes to tell us what happened after a hire. No personal information leaves HR Worker.

Read the API reference Ask for developer access
Overview Integrate with Workday Integrate with Paradox API calls

Getting started

During the pilot, HR Worker sets up developer accounts for the companies it works with. Everything you build sees your company's data only.

Step 1

Get a developer account

Ask your company’s HR Worker contact. HR Worker invites you, and you sign in with a code sent to your email.

Step 2

Create a key

Name it, choose read only or read and write, and copy it. It is shown once.

Step 3

Make your first call

GET https://hrworker.com/api/v1/stores
Authorization: Bearer hrw_live_…

Integration guides

Examples of how a team that already runs these systems connects them to HR Worker. Your own team builds and runs the integration.

How to integrate with Workday

HR system

Bring HR Worker hires into Workday, and send starts and changes back.

  1. 1Read new hires. Your scheduled integration calls GET /hires and creates a pre-hire in Workday for each one, keyed by the HR Worker applicant id.
  2. 2Match the store. Map each HR Worker store number from GET /stores to your Workday location once.
  3. 3Confirm the start. When the hire is completed in Workday, call POST /hires/{id}/start with the first working day.
  4. 4Report changes. On a transfer or termination, call POST /hires/{id}/status with moved, quit, fired, laid off or on leave and the effective date.

Workday is a trademark of its owner. HR Worker is not a Workday partner; this is an example pattern.

How to integrate with Paradox

Recruiting assistant

Keep your recruiting assistant in step with the candidates HR Worker sends.

  1. 1See open needs. Read GET /postings so your team knows which store roles HR Worker is filling, and avoids running the same need twice.
  2. 2See booked interviews. Read GET /interviews by store and date, so managers' calendars in both systems agree.
  3. 3Close the loop on starts. When onboarding confirms the first day, call POST /hires/{id}/start.
  4. 4Compare results. Read GET /funnel per store to set HR Worker's pipeline beside your own.

Paradox is a trademark of its owner. HR Worker is not a Paradox partner; this is an example pattern.

The ten API calls

Reads return applicant ids, first names and last initials. Never a phone number, email or address.

Eight reads · monitor what is happening

GET/storesStores and districts
GET/postingsOpen needs, openings, start-by
GET/postings/{id}Booked against needed
GET/interviewsInterviews by store and date
GET/interviews/{id}Outcome and scorecard label
GET/hiresHires and first working days
GET/funnelPipeline counts per store
GET/reasonsApproved decline reasons

Two writes · update the outcomes

POST/hires/{id}/startThe first day happened, or didn't
POST/hires/{id}/statusMoved, quit, fired, laid off, on leave

Keys and limits

  • Keys belong to your company and see only its data.
  • Read-only keys cannot write.
  • Every call is logged; your developer zone shows the log.
  • 60 requests a minute per key, 100 items a page.
Read the full reference