This content provides an early look at an upcoming extension to the SEEK API. You may use it to scope integration effort, but the features described are not fully implemented and may be adjusted ahead of a production release.
Please check with your SEEK contact before starting any build work described here.
When a candidate applies using Apply with SEEK they may have a resume attached to their profile
Partners can download attachment files associated with a particular candidate profile to pre-fill the resume field.
The
candidateProfile query from Step 3 should be used to retrieve the URL of any profile attachments when retrieving the rest of the candidate details.
If a resume is available, the attachments object should be populated with the URL of the resume as shown below.JSON
Copy
{"candidateProfile": {
// ... other candidate details
"attachments": [
{
"descriptions": ["Candidate resume"],
"seekRoleCode": "Resume",
"url": "https://graphql.seek.com/anzPublicTest/applications/4QM5fWQbdekL9gPtPZrzex/attachments/7wS9uaWkwNrz4L5EUjNoBpVHCo61gaTSTdqiEeqxPVAk"
}
]
}
}Because GraphQL does not efficiently support binary data, the attachment itself is provided over HTTPS.
Each attachment has a unique download URL provided in the
url field of the GraphQL response.During the Apply with SEEK flow your software should download attachments via your server using a partner token.
Attachment files have additional metadata returned in standard HTTP headers.
These headers can be parsed by your software or passed to the hirer’s browser when they download the attachment.
You can use the HTTP
HEAD method to retrieve an attachment’s metadata without downloading its contents.
This is useful to display the attachment’s metadata before downloading it.The
Content-Disposition header contains the attachment’s original filename encoded using RFC 6266 .We recommend parsing the filename using a library or framework that supports RFC 6266 .
This ensures your software is robust against filenames containing spaces, quotes or other special characters.
The
Content-Length header indicates the size of the attachment in bytes.
This can be retrieved using the HTTP HEAD method to display the attachment’s size before downloading it.The
Content-Type header indicates the file format of the attachment.
Alternatively, you can extract the attachment’s file extension from its Content-Disposition.The currently supported file formats are:
Content-Type | File format | Extension |
|---|---|---|
application/msword | Microsoft Word 97-2004 | .doc |
application/vnd.openxmlformats-officedocument.wordprocessingml.document | Microsoft Word (OpenXML) | .docx |
application/rtf | Rich Text Format (RTF) | .rtf |
application/pdf | Portable Document Format (PDF) | .pdf |
text/plain | Plain text | .txt |
The
Last-Modified header contains the date the attachment was uploaded or generated.SEEK processes attachments to reduce the risk to hirers reviewing candidate applications:
- Attachments are scanned for viruses before the candidate application is made visible to partners. Any files containing viruses are removed from the candidate application.
- Attachments may be modified to remove dangerous content such as macros or phishing links.
The precise details of SEEK’s attachment processing are proprietary and subject to change.
SEEK continuously improves its processes in response to new threats.