Skip to main content
TapTalent produces candidate data, status transitions, and PDF documents across the hiring lifecycle—applications, pipeline progress, AI interviews, offers, and onboarding. There are two ways to get them into your ATS/HRIS.

​
Option comparison

​
Option 1: Managed direct delivery

TapTalent pushes candidate fields, documents, and status updates directly into your HRIS through your HRIS’s own API, using integration credentials you provision and a field and document-category mapping agreed during setup.
Managed direct delivery is configured per client engagement with TapTalent—contact support@taptalent.ai. It is not configurable through the Partner API.

​
What can be delivered

​
Stage-to-disposition mapping

Hiring pipelines in TapTalent are custom per company and job (Pipelines). During setup, you map each TapTalent pipeline stage—by stage ID and/or stage type (SOURCED, APPLIED, ASSESSMENT, SCREEN, SHORTLISTED, OFFER, ONBOARDING, HIRED)—to a disposition or status value in your HRIS. Every stage change then triggers the mapped update; stages you leave unmapped are skipped. Rejections map to your rejected disposition, with the rejection reason included where your HRIS accepts one. Example mapping (values are yours to define):

​
Correlating with your requisitions

To land records on the right requisition in your HRIS, give each TapTalent job a requisition reference using a custom field:
  1. Create a job custom field (e.g. “HRIS Requisition ID”) with Create Custom Field (entityType: "job").
  2. Set its value per job with custom field values.
  3. Read it back in the customFields map of Get Job.
TapTalent includes the mapped requisition reference in every HRIS push.

​
What you provide at setup

  • HRIS API credentials for an integration user/service account, scoped to the agreed operations (write candidate fields, upload and tag candidate documents, move candidate status).
  • Your HRIS tenant/endpoint identifiers.
  • The field mapping (which TapTalent values go to which HRIS fields).
  • The document-category mapping (where each PDF type is filed).
  • The stage-to-disposition mapping.
  • The name of the requisition custom field.

​
Option 2: Self-serve webhooks and pull APIs

Your integration consumes webhooks and pull APIs and performs the writes to your HRIS itself. Every delivery trigger in the table above has a webhook event, and every document is retrievable as a fresh time-limited PDF URL. See the event catalogue and the “Typical actions in your system of record” mapping on Agentic Onboarding.

​
Choosing an option

The options are not exclusive: webhooks keep firing under managed delivery, so you can start with managed direct delivery and add your own event-driven processing later—or run both, using webhooks for monitoring while TapTalent performs the HRIS writes.