Server-side integration

Connect the kiosk to Manatal without exposing credentials.

The Manatal API token belongs in the hosting platform’s private environment variables—not in this page, the browser, or any JavaScript file.

Keep separate: W-4, NC withholding, Form I-9, Social Security numbers, bank routing/account numbers, medical records, drug-test results, and full background reports are not routed to normal Manatal candidate attachments.

Integration status

Activation checklist

1. Obtain Manatal Open API accessIn Manatal, open Administration → Features → Open API. Enterprise Plus includes API access; other plans may need Manatal support.
2. Generate a dedicated API tokenDo not use or share your normal Manatal password.
3. Configure the hosting environmentCopy .env.example to .env for local testing, or enter the variables in Replit/Render/Vercel secrets.
4. Begin in dry-run modeUse MANATAL_MODE=dry-run to verify the kiosk, encrypted queue, PDFs and field mapping without creating candidates.
5. Add job/custom-field mappingsEdit config/manatal-mapping.json using the job IDs and custom-field keys from your own Manatal account.
6. Enable live modeSet MANATAL_MODE=live, restart the server, test the token, and submit one fake applicant before using real records.

What the live connection does

Duplicate detection

Searches by email, then phone. Existing candidates are updated instead of blindly duplicated.

Candidate creation

Transfers name, email, phone, address, current employer/position and configured custom fields.

Documents

Uploads the résumé and server-generated application/onboarding PDFs through temporary HTTPS file links.

Job matching

Optionally creates a candidate/job match using category-to-job mappings or a default Manatal job ID.

Recovery

Failed submissions remain in an encrypted retry queue and can be resent from the staff dashboard.

Restricted payroll

Tax, I-9 and banking workflows remain separate and are represented only by completion status.