POST
/
ats
/
applications
/
{application_id}
/
attachments
{
  "status": "success",
  "data": {}
}

If adding an attachment to an application is not supported by the integration, the attachment will be added to the candidate instead.

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

Example Request Body

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

Authorizations

Authorization
string
headerrequired

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

application_id
string
required

POST /ats/applications/:application_id/attachments parameter

Body

application/json
attachment
object
required
remote_fields
object

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

Response

200 - application/json
status
enum<string>
required
Available options:
success
data
object
required