# Recruitee integrations: candidates and offers

> Create a candidate and create an offer in Recruitee, and start a workflow when Recruitee sends “Candidate created”.

**Canonical page:** https://tray.ai/connectors/recruitee-integrations/
**Categories:** Human resources
**Connects through:** HTTP Connector

## Overview

Recruitee is an applicant tracking system from Tellent where hiring teams publish jobs, collect applications and move candidates through hiring pipelines together. Tray.ai connects to Recruitee through the HTTP Connector, so your workflows can call the Recruitee API alongside the rest of your stack.

## Use cases

### Candidates

Read and create candidates in Recruitee from any Tray.ai workflow. The Recruitee API covers calls such as create a candidate and search candidates.

- Create a candidate
- Search candidates
- Add candidate profile fields

### Offers

Read and create offers in Recruitee from any Tray.ai workflow. The Recruitee API covers calls such as list offers and get an offer.

- List offers
- Get an offer
- Create an offer

### Careers site

Read and update careers site in Recruitee from any Tray.ai workflow. The Recruitee API covers calls such as list published jobs and apply for a job.

- List published jobs
- Apply for a job

### Recruitee events

Start a Tray.ai workflow the moment something happens in Recruitee. Recruitee sends events such as candidate created and candidate assigned to a Tray.ai webhook trigger.

- Candidate created
- Candidate assigned
- Candidate moved in pipeline

## Challenges Tray.ai solves

### Keeping Recruitee credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Recruitee credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Recruitee API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Recruitee API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Recruitee?

Yes. Tray.ai connects to Recruitee through the HTTP Connector, which calls the Recruitee API directly. Any call the Recruitee API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Recruitee?

The Recruitee API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Recruitee connector?

Recruitee runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Recruitee connector from the Recruitee API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/