resumes.create
Upload a résumé
- Request
- POST
/api/v1/resumes - Scope required
resumes:write- Effect
- Changes data. Send an Idempotency-Key if you might retry it.
- Acts on
- Acts on the account’s own job search.
- MCP tool
resumes_create- Environment
- Live and sandbox alike.
- Request body
- multipart/form-data. A file part is sent as fileName, contentType and contentBase64.
- Body size
- Up to 14 MiB, rather than the usual 1 MiB.
What it does
Stores a new résumé on this account. Over REST, send it as `multipart/form-data` with a `file` part and a `name` field; a tool call sends the same thing as JSON, with `file` as `{ fileName, contentType, contentBase64 }`. The file must be a PDF, DOC or DOCX and no larger than ten mebibytes — anything else is refused with 415 or 413. The `name` is what you will recognise it by later; the file name is kept as it arrived. Uploading does not attach it to anything, so follow with `applications.attach_resume` to record which job it was sent for, and read it back with `resumes.get`.
Response
- createdAt
- string, required
- fileName
- string, required
- fileSizeBytes
- integer, required
- fileType
- string, required
- id
- string, required
- name
- string, required
- updatedAt
- string, required
Examples
Upload the platform engineering résumé
curl -s -X POST https://www.jobapplicationtracking.com/api/v1/resumes \
-H "Authorization: Bearer $JAT_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Platform engineering",
"file": {
"fileName": "riley-bennett-platform.pdf",
"contentType": "application/pdf",
"contentBase64": "JVBERi0xLjcK"
}
}'{
"id": "rs_5",
"name": "Platform engineering",
"fileName": "riley-bennett-platform.pdf",
"fileType": "application/pdf",
"fileSizeBytes": 148221,
"createdAt": "2026-01-04T09:30:00.000Z",
"updatedAt": "2026-01-04T09:30:00.000Z"
}