---
title: "Create Candidate Attachment"
method: POST
path: "/api/ats/v1/candidates/{candidate_id}/attachments"
tags: ["Candidate"]
---

# Create Candidate Attachment

`POST /api/ats/v1/candidates/{candidate_id}/attachments`

Uploads an attachment for a given candidate.

## Path parameters

- `candidate_id` string, required

## Headers

- `x-connector-token` string, required

## Request body

- AtsAttachmentWrite — The AtsAttachmentWriteForCandidate object is used to represent a file attachment linked to a candidate's application within the ATS.
  - `file_name` string, nullable — The name of the file attached.
  - `file_url` string, uri, nullable — The URL where the file is stored and can be retrieved.
  - `attachment_type` 'RESUME' | 'COVER_LETTER' | 'OFFER_LETTER' | 'OTHER' | '-', nullable — The type of attachment. If the value is not one of the defined enum values, the original value passed through will be returned.
  - `file_content` string, nullable — File in base64 format
  - `content_type` string, nullable — The MIME type of the file (e.g., 'application/pdf', 'image/png').
  - `candidate` string, uuid, nullable — The candidate to whom the attachment belongs.
  - `remote_user_id` string, uuid, nullable — The id of user using the integration

## Response `200`

Successful Response

- unknown

## Other responses

- `401` — Missing or invalid bearer authentication credentials.
- `403` — The credentials are valid but do not permit access to this resource, e.g. a connector token used on a different API category or a model whose writes are disabled.
- `404` — The requested resource was not found.
- `422` — Validation Error
- `429` — Rate limit exceeded.

---

[API](https://skmtc.net/bindbee/apis/bindbee-apis.md) · [All operations](https://skmtc.net/bindbee/apis/bindbee-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/bindbee/bindbee-apis/revisions/7da10dc93a21/schema)