// loading
Slack notifications, REST + webhooks, an iframe embed for your career site, and direct connectors for Greenhouse, Lever, Ashby, and Workday: the four ATSes recruiters actually buy. Plus the rest of the things people search for: SSO, sending domains, reply-ingest, calendar. The long version is below.
most connectors are on the recruiter seat · ats connectors on Volume
Pull job postings, sync candidates back, attach the OpsTicket score as a scorecard.
Push score + replay link as a feedback form. Two-way candidate sync.
Native scorecard. Replay link in the candidate timeline. Stage map editable.
Recruiter-side connector with the long-form integration we don’t want to make jokes about.
Stage-advance pings to channel · DM the recruiter when a candidate reaches Shortlist · /opsticket slash commands.
Same surface as Slack · channel pings + adaptive cards · in preview with three design partners.
Two-way busy-block sync · the scheduler reads from any number of calendars in a recruiter’s account.
Same surface as Google · outlook calendar + invites · works with the calendar of a delegated executive assistant.
Drop the assessment into your own career-site posting. Themed via CSS variables. Score posted back via webhook.
Read candidates, sessions, rubrics, replays. Write invites, stage changes, notes, tags. Cursor-paginated. Bearer-auth.
Subscribe to every stage change, every score, every replay-watched event. Signed payloads · idempotency keys · retries.
SAML 2.0 · JIT provisioning · SCIM for seat management.
SAML + OIDC · conditional access policies respected.
SAML 2.0 · domain-wide enrollment supported.
Bring your own sending domain. We don’t proxy through opsticket.com unless you really want us to.
Reply detection · pauses the sequence the moment a candidate replies in their inbox.
We don’t try to replace your ATS: we add to the candidate record inside it. Score, time-on-task, the five rubric dimensions, and a stable URL to the replay. Recruiters who live in Greenhouse stay in Greenhouse: they just have a real signal sitting where the résumé summary used to sit.
| OpsTicket field | → | Greenhouse field |
|---|---|---|
| candidate.email | → | candidate.email |
| session.score | → | scorecard.overall |
| session.rubric.* | → | scorecard.section[*] |
| session.replay_url | → | scorecard.note · pinned |
| pipeline.stage | → | application.stage · mapped |
| notes[*].body | → | interview.notes · markdown |
POST /v1/invites HTTP/1.1
Host: api.opsticket.com
Authorization: Bearer ops_live_94e2c7...
Idempotency-Key: csv-upload-2025-04-22-1
Content-Type: application/json
{
"posting_id": "psg_helpdesk_lead_sample",
"sequence_id": "seq_phone_screen",
"candidates": [
{"email": "[email protected]", "name": "Devon P."},
{"email": "[email protected]", "name": "Aisha O."}
]
}
-> 202 Accepted
{ "queued": 2, "dup": 0, "bad": 0, "session_id": "csv_a14b" }Bearer auth. Cursor pagination. Idempotency keys on every write. Signed webhook payloads. Retries with exponential backoff. We don’t have a GraphQL because nobody on the team has been begging for it. If you’re embedding OpsTicket Assess into your own platform, iframe + the API does it.
If the integration you want isn’t on the page above, it’s either on the roadmap (Microsoft Teams, BambooHR, Rippling-as-source) or it’s not. We won’t pretend a webhook is a “BambooHR integration”: it isn’t. The webhook can probably do the job, but we’d rather call it a webhook.
The Greenhouse connector drops the score into the scorecard where the résumé summary used to sit. That’s the whole sell.
from product brief · 2026private beta · no credit card · sandbox in under a minute