Upload Resume
Resumes
Upload Resume
Upload a resume file to store it and get an id you can reuse for semantic job matching.
POST
Upload Resume
Upload Resume is the stored counterpart to Embed Resume.
/embed is stateless and returns only a vector, whereas /upload persists the resume and returns an _id (a MongoDB ObjectId) that doubles as the artifact_id for Vector Search (search_type: "resume") and Neural Search (vector.artifact_id).
The typical flow is upload → parse → use _id as artifact_id. (The Python SDK’s resumes.upload_and_parse performs the upload and parse in a single step.)
Endpoint
Authentication
Your Hirebase API key. Required — this is an always-authenticated endpoint, like the other resume endpoints.
Request
Content-Type:multipart/form-data
Note:
- The request must include exactly one file.
- Supported file types: PDF, DOC/DOCX, plain text, HTML.
- Maximum file size: 5 MB.
- The uploaded file part must carry a correct
Content-Type(e.g.,application/pdf,text/plain,text/html, or the DOCX MIME type). Multipart requests that omit it (some HTTP clients default toapplication/octet-stream) are rejected with400 File must be PDF or Word document, even for otherwise-valid files. cURL sets this automatically from the file extension.
The resume file to upload.
Response
Resume record id. Use this value as the
artifact_id for downstream Vector Search and Neural Search.Owner of the record (the account associated with your API key).
Stored file URL for the uploaded resume.
Structured resume fields. Empty/
null until you call Parse Resume; populated afterward.Record status.
"uploaded" immediately after upload, "parsed" after parsing.Creation timestamp (ISO 8601).
Last-updated timestamp (ISO 8601).