/

Docs
History
Schema
Generate

Filter operations

Clients37

Companies1

CompanySettings10

CompanySignUp3

Connect5

ContractJobs19

Contractors15

CostCenters5

CustomFields4

Customizations1

Dashboards12

Diagnostics9

DirectHires6

EarningCodes4

Employees2

Entities6

Erp2CompanyEvents1

Erp2Lookups9

Erp2PlacementDocuments1

Erp2Webhook1

Everee1

Exports3

FieldMappings8

JobAdder1

Layouts3

Notifications1

OAuth4

OvertimeRules1

PayBillItem2

PayBillItemDetail2

PayCodes8

Placements7

get/jobdiva/v1/placements/reconciliation
post/jobdiva/v1/placements/link
post/jobdiva/v1/placements/importImports one JobDiva placement as a Bilflo contract job. DRY RUN BY DEFAULT. Pass dryRun=false to write. That direction is deliberate: this is the first write path into a live customer account, there is no staging environment, Bilflo has no duplicate guard on jobs, and a contract job cannot be deleted - only deactivated. So a caller has to ask for the write rather than remember to ask for safety. A dry run reports exactly what the job would be built from and every reason it cannot be created yet. It refuses rather than filling a gap with a default: a guessed pay rate bills wrongly and a guessed W2-versus-1099 is a tax problem, so "no job" is the better failure.
post/jobdiva/v1/placements/updateRe-reads an already-imported placement and applies what changed in JobDiva to the existing Bilflo job. dryRun defaults TRUE, like import, and for a stronger reason: this writes to a live job that may already be billing, so the operator sees the diff first.
post/jobdiva/v1/placements/close-terminatedCloses Bilflo jobs whose JobDiva placement was terminated or cancelled. Sweeps the whole integration unless placementId is given. dryRun defaults TRUE: this closes live jobs, and a future-dated termination deliberately only moves the end date rather than closing, so the diff is worth reading first.
get/jobdiva/v1/placements/previewHydrates a few already-polled starts and reports what JobDiva returned. READ ONLY - creates and updates nothing in Bilflo. The BI hires feed is a discovery record and nothing more: every row is just PLACEMENTID and CANDIDATEID. Everything a contract job needs lives in searchStart, which no code has ever called, so JobDivaStartDto is a transcription of JobDiva's Swagger rather than observed truth. This endpoint is how that gets confirmed before an assembler is built on it. GET so it is harmless to retry, but it does make one outbound searchStart call per start, so keep the limit small.
post/jobdiva/v1/placements/unlink

PrismHR8

Processors1

Query Engine3

Reports1

Subscriptions2

Transactions7

Users18

Webhook2

Workflows32

Placements

Changes to POST /jobdiva/v1/placements/unlink

post/jobdiva/v1/placements/unlink

Oct 19, 20269a6c8d6deedc Revision changes
- info
  endpoint added