Skip to main content
POST
Create Candidate Attachment
Currently this functionality is available for Success Factor and Teamtailor
🚨 Note: File size cannot exceed 5 MB.

For SAP Success Factor Integration

If integrating with SAP_SUCCESS_FACTOR, the request body must only contain:

For Teamtailor Integration

If integrating with Teamtailor, the request body must only contain:

Authorizations

Authorization
string
header
default:<BINDBEE_API_KEY>
required

Your Bindbee API key, sent as Authorization: Bearer <BINDBEE_API_KEY>. Required on every request.

X-Connector-Token
string
header
default:<CONNECTOR_TOKEN>
required

The connector token for one customer's connection. This is not your Bindbee API key. Required on requests that read or write a single customer's data.

Path Parameters

candidate_id
string<uuid>
required

Body

application/json

The AtsAttachmentWriteForCandidate object is used to represent a file attachment linked to a candidate's application within the ATS.

file_name
string | null

The name of the file attached.

Example:

"resume.pdf"

attachment_type
string | null

The type of attachment. If the value is not one of the defined enum values, the original value passed through will be returned.

Example:

"RESUME"

file_url
string<uri> | null

The URL where the file is stored and can be retrieved.

Required string length: 1 - 2083
Example:

"https://example.com/path/to/resume.pdf"

file_content
string | null

File in base64 format

Example:

"SGVsbG8sIFdvcmxkIQ=="

content_type
string | null

The MIME type of the file (e.g., 'application/pdf', 'image/png').

Example:

"application/pdf"

candidate
string<uuid> | null

The candidate to whom the attachment belongs.

Example:

"018b4bfb-5ece-70b1-ad5e-862a9433aa65"

remote_user_id
string<uuid> | null

The id of user using the integration

Example:

"018b4bfb-5ece-70b1-ad5e-862a9433aa65"

Response

Successful Response