Apply to DHS for E-Verify Web Services access; upon approval, receive the Interface Control Agreement (ICA) which contains the technical specifications, WSDL or REST schema, and test environment credentials.
Implement the software interface per the ICA, extracting Form I-9 data from your HRIS and transmitting it to E-Verify using either the SOAP or REST communication protocol as supported.
Test all case creation, status query, and case closure flows thoroughly in the E-Verify test environment before requesting production access.
In production, create E-Verify cases automatically when a new hire completes Form I-9 Section 2, passing the employee's document type, document number, and personal data fields as required by the ICA.
Poll the case status endpoint at appropriate intervals to retrieve case results and propagate them back to the HRIS employee record.
Implement handlers for all possible case result codes including Employment Authorized, TNC, Final Nonconfirmation, and DHS or SSA referral states.
Known gotchas
Web Services access requires a formal agreement with DHS and a technical review; plan for several weeks of lead time before integration can go live.
The ICA is the authoritative technical contract — E-Verify may update field requirements or result codes between ICA versions; monitor version notices and test updates before deploying.
E-Verify Web Services must not be used to pre-screen candidates before a job offer is extended; case creation is only permitted after hire and Form I-9 completion.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp