Approved access to
Xaigh labor rails.
Enterprise teams can request scoped integration access for job posting, employer work setup, and workforce updates. Keys are reviewed and issued manually so hiring, pay, and worker trust stay protected.
Request access
Send company, contact, use case, scopes, volume, and callback URL. We review the request and reply with next steps.
Manual review
A person reviews the request, access needs, risk, and readiness.
Key issued by hand
Approved keys are set up on our side, limited to specific tasks, and can be revoked without app changes.
Scoped production calls
Enterprise systems call approved Xaigh job and employer APIs with simple, traceable requests.
Build against the approval path first.
The first public contract is the access request and scoped key check. Live job-writing access is granted only after Xaigh reviews use case, employer ownership, volume, and failure handling.
Xaigh accepts integration-key auth only after the key is manually configured as approved.
Scopes stay limited, so a jobs key cannot call payroll or unrelated employer APIs.
Integration credentials are server-side only; browser clients stay away from secret headers.
await fetch("https://www.xaigh.com/api/integrations/access-requests", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
companyName: "Northline Warehousing",
contactName: "Maya Patel",
contactEmail: "[email protected]",
useCase: "Post approved warehouse shifts from our labor plan.",
requestedScopes: ["jobs:write", "employer:read"],
monthlyVolumeEstimate: 2500,
callbackUrl: "https://example.com/xaigh/events"
})
});The client owns the job. Xaigh runs the work.
Xaigh mirrors the employer posting, keeps local work rules, and closes stale jobs only when the client hiring feed proves they are gone.
Protected job fields
Source
Client hiring system
Stale check
24h watch
Apply mode
Redirect or forward
Review
Source details kept
Client system owns
Job details, open state, pay range, apply path
The employer system stays in charge of the posting. Xaigh will not overwrite it from the posting page.
Xaigh rules
Fill plan, matches, check-in, payroll handoff
Xaigh keeps the work rules in place: offers, site checks, documents, readiness, and worker audience.
Change trail
Created, changed, closed, and missing job events
Every change keeps provider, source file, status, and close rule details for review.
Trusted job feed
Client hiring system
Workday, Greenhouse, Lever, Ashby, iCIMS, or a custom feed sends the active roles.
Clean Xaigh copy
One stable job record
Xaigh keeps title, pay, place, needs, apply link, job link, status, and requisition tied together.
Work items attach
Xaigh work layer
Matches, messages, fill, site checks, documents, worker audience, readiness, and payroll signals attach without rewriting the source job.
Close only on source match
Missing from client feed
When the client feed no longer shows a role, Xaigh can close it locally and stop matching.
Employer view
Live hiring status
Provider count, open and closed roles, stale feeds, and ownership rules feed the employer view.
import { createXaighClient } from "@xaigh/server-sdk";
const xaigh = createXaighClient({
baseUrl: "https://api.xaigh.com",
integrationKey: process.env.XAIGH_INTEGRATION_KEY
});
await xaigh.post("/v1/integrations/jobs/post", {
employerAccountId: "employer_acct_123",
title: "Warehouse closeout crew",
slots: 12,
startsAt: "2026-06-18T08:00:00.000Z"
}, { idempotencyKey: "shift-plan-2026-06-18-a" });Key access is part of the product.
Xaigh powers real work: open shifts, employer approvals, readiness checks, and closeout. Access stays locked until the setup can prove ownership and recovery behavior.
Manual approval boundary
A request is not a key. Live access requires approval, setup, and a clear rollback path.
Request reviewed access.
Bring the use case, task types, estimated volume, callback URL, and the failure mode your team needs covered.
Start access review