Integrate with the Equifax-owned LawLogix Guardian REST API to trigger Form I-9 Section 1/Section 2 completion and track E-Verify case results from an external HRIS/ATS.
domain: developer.lawlogix.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain OAuth2 credentials (Client ID, Client Secret, Username, Password) from your Guardian implementation specialist.
POST client_id, client_secret, username, and password using the OAuth2 resource-owner password grant to the Guardian /oauth2/access_token endpoint to receive an access_token, refresh_token, and expiry (expires_in).
POST the new hire's data (firstName, lastName, emailAddress, startDate, locationId, onboardingType, integrationCandidateId, employeeReturnUrl) to /v1/partners/i9s/section1 with the access token as a Bearer header to initiate the I-9 and receive an i9Section1Link.
Redirect the new hire to the returned i9Section1Link to complete Section 1 inside the Guardian UI.
Consume Guardian's PATCH callback (i9Status, i9NextStep, i9NextStepDueDate, i9Url) to know when Section 2 is ready, then route the Guardian user (verifier) to i9Url to countersign Section 2.
When E-Verify is enabled, consume the E-Verify PATCH callback (eVerifyStatusCode, eVerifyResolutionCode, eVerifyNextStep, eVerifyNextStepDueDate, eVerifyUrl) to track case resolution through to closure.
Known gotchas
Guardian sends only the current state of the I-9/E-Verify case with each callback — not every intermediate status is guaranteed to be delivered, so don't build logic that assumes every transition arrives.
Rehiring a former employee only works through this workflow if their existing Guardian record is in a terminated state; otherwise employee creation will conflict with the existing record.
Refreshing a token still requires resending client_id, client_secret, and username alongside refresh_token — it is not a bare token-only refresh like many OAuth2 implementations.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?