Bulk Ingest (REST)

Blocked from publishing until the auth and gating checklist in Authentication & Scopes lands.

Purpose

Typed REST routes for loading candidates and jobs in bulk, plus a status route to poll progress.

Endpoint	Why
`GET /api/health`	Liveness check, no auth required
`POST /api/candidates/bulk-upload-resumes`	Typed candidate ingest, `write` scope
`GET /api/candidates/bulk-upload-status/{jobId}`	Poll bulk-upload progress
`POST /api/jobs/add-by-file`	Typed job ingest from a JD file, `write` scope

POST /api/upload is not published. Generic blob upload is an abuse and quota risk. Partners must ingest through the typed routes above.

How do we track a bulk upload?

Poll GET /api/candidates/bulk-upload-status/{jobId} until it reports complete.

Can we upload arbitrary files?

No. The generic upload route is not published. Use the typed candidate and job ingest routes.

What scope do ingest routes need?

The write scope. The health check needs no auth.

The single-record CRUD behind these batch routes.

The pattern for polling asynchronous results.

⌘I