Request import file upload
Returns a presigned upload URL + fileKey for a resume file, for callers that cannot extract text themselves.
/v1/imports:uploadAuthorization
Credential
oauth_userRequired scopes
profile:importRequest body
JSON · application/json
contentTypestringrequiredapplication/pdf
sizeBytesintegerrequiredImplementation note
PUT the raw file bytes to `uploadUrl` (with the declared Content-Type) before it expires, then call `import-create` with `{ source: "resume", fileKey }`. PDF only today, max 10 MB — the parse worker re-checks size and magic bytes server-side. Agents that can already read the file (e.g. MCP clients that cannot PUT binaries anyway) should skip this and send extracted text as `content` instead.
Error responses
400Invalid request
The request body was missing, malformed, or failed schema validation. Field-level problems are listed under `issues`.
401Authentication required
No valid credentials were supplied. Attach a Bearer access token and retry.
402Upgrade required
The authenticated user's plan does not include this capability. `feature` names the gated capability, `requiredPlan` the cheapest plan that unlocks it, `currentPlan` the user's plan today, and `upgradeUrl` links to checkout. This is a plan gate, not a transient error — retrying without upgrading fails again; surface `upgradeUrl` to the user instead. Dormant until a plan that grants the feature is active, so a route that documents it may not currently return it.
403Insufficient scope
The token is valid but lacks the OAuth scope (or token kind) this endpoint requires.