Coming soonAshby
Send an EasyEnv role from an Ashby interview plan, and see the status and the result on the candidate in Ashby.
Setup guide →
Send EasyEnv interviews from your applicant tracking system and get the results back on the candidate. Building your own product? Connect it through the EasyEnv API.
Recruiters send an EasyEnv interview from the ATS they already use, and see the outcome on the candidate. If your team uses one of these and wants early access, tell us.
Coming soonSend an EasyEnv role from an Ashby interview plan, and see the status and the result on the candidate in Ashby.
Setup guide →
Coming soonOrder EasyEnv interviews from a Greenhouse job, without leaving it.
Coming soonSend EasyEnv assessments from Pinpoint, and see the outcome on the candidate.
Everything the EasyEnv dashboard does goes through a REST API, and your product can use it too.
List the roles in an account, invite a candidate to an interview, follow their progress, and read the reviewer's decision. Base URL: api.easyenv.io/v1.
Each customer generates a service token on their EasyEnv profile and gives it to your product, with their account ID. Send them on every call as X-Service-Token and Account-ID.
Not available yet. Poll an interview for its status instead; every few minutes is enough. If you need webhooks, tell us which events.
Email [email protected] with "Partner integration" in the subject. We reply within one business day.
# 1. The roles a recruiter can pick from
curl https://api.easyenv.io/v1/interviews/ \
-H "X-Service-Token: $TOKEN" -H "Account-ID: $ACCOUNT"
# 2. Invite the candidate. EasyEnv emails them the interview.
curl -X POST https://api.easyenv.io/v1/interviews/$ROLE/interview-items/ \
-H "X-Service-Token: $TOKEN" -H "Account-ID: $ACCOUNT" \
-F type=offline -F [email protected] \
-F start_date=2026-09-18 -F end_date=2026-09-25
# 3. Poll it until "status" is "review_completed"
curl https://api.easyenv.io/v1/interviews/$ROLE/interview-items/$INTERVIEW/ \
-H "X-Service-Token: $TOKEN" -H "Account-ID: $ACCOUNT"
# "review_status": "accepted" or "rejected", the reviewer's decisionTell us which one. Customer requests decide which integration we build next.