POST
/
ats
/
candidates
/
{candidate_id}
/
attachments
curl --request POST \
  --url https://api.kombo.dev/v1/ats/candidates/{candidate_id}/attachments \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'X-Integration-Id: <x-integration-id>' \
  --data '{
  "attachment": {
    "name": "Frank Doe CV.txt",
    "data": "SGkgdGhlcmUsIEtvbWJvIGlzIGN1cnJlbnRseSBoaXJpbmcgZW5naW5lZXJzIHRoYXQgbG92ZSB0byB3b3JrIG9uIGRldmVsb3BlciBwcm9kdWN0cy4=",
    "type": "CV",
    "content_type": "text/plain"
  }
}'
{
  "status": "success",
  "data": {}
}

We recommend using the add attachment to application endpoint instead.

We realized that in practice it was always more about adding attachments to applications instead of candidates, so we created a new, more aptly named one that you should use instead: add attachment to application

This endpoint requires the permission Add attachments to be enabled in your scope config.

​
Example Request Body

{
  "candidate_id": "GRKdd9dibYKKCrmGRSMJf3wu",
  "attachment": {
    "name": "Frank Doe CV.txt",
    "data": "SGkgdGhlcmUsIEtvbWJvIGlzIGN1cnJlbnRseSBoaXJpbmcgZW5naW5lZXJzIHRoYXQgbG92ZSB0byB3b3JrIG9uIGRldmVsb3BlciBwcm9kdWN0cy4=",
    "type": "CV",
    "content_type": "text/plain"
  }
}

Authorizations

​
Authorization
string
header
required

Create an API key on the Secrets page in the Kombo dashboard.

Headers

​
X-Integration-Id
string
required

ID of the integration you want to interact with.

Path Parameters

​
candidate_id
string
required

The Kombo ID of the candidate you want to add the attachment to.

Body

application/json
POST /ats/candidates/:candidate_id/attachments request body
​
attachment
object
required
​
remote_fields
object

Additional fields that we will pass through to specific ATS systems.

Response

200
application/json
POST /ats/candidates/:candidate_id/attachments Successful response
​
status
enum<string>
required
Available options:
success
​
data
object
required