Native Zapier and Make apps with full triggers, actions, and
searches. A public REST API for the developer path. Outbound
webhooks shipping soon. Plug TalentGleam into your HRIS, payroll, BI,
or anything in your stack.
Both Zapier and Make ship as native TalentGleam apps with full triggers,
actions, and searches. Fire a Zap when a candidate is hired and
update your HRIS automatically. Look up a candidate from a Slack
slash command. Create a new candidate in TalentGleam from a contact-form
submission. No code, no glue scripts.
Full triggers, actions, and searches on both platforms
Connect to 9,000+ tools without writing a line of code
Fire Zaps on hire, stage move, or new candidate events
02
Public REST API for the developer path.
Everything in TalentGleam is reachable through a documented REST API.
Generate a personal access token in your workspace settings, pass
it in the Authorization header, and read or write candidates,
jobs, applications, and stage moves. Useful for custom dashboards,
in-house automation, or building your own integration on top of
TalentGleam.
Generate a personal access token from workspace
settings
Read and write candidates, jobs, applications, and stage
moves
Scoped to the user's permissions — no over-privileged
keys
03
Outbound webhooks for real-time events (shipping soon).
When webhooks ship, TalentGleam will post events to a URL you define: new
candidate, stage moved, hired, rejected, and more. Useful for
piping data into your data warehouse, your HRIS, or any system
that prefers push over poll. No more periodic Zap runs just to
catch a state change.
Push events to any URL you define
Covers new candidate, stage moved, hired, and rejected
No more periodic polling — pure push when state changes
WHAT YOU CAN DO
Four surfaces, one integration story.
Native Zapier app
Triggers, actions, and searches across candidates, jobs,
applications, and stage moves. Connect TalentGleam to the 9,000+
tools Zapier supports.
Native Make app
The same TalentGleam surface, on Make instead of Zapier. Use the
platform your team already runs scenarios on.
Public REST API
Documented endpoints across the TalentGleam data model. Personal
access token auth, generated in workspace settings.
Outbound webhooks (soon)
Push real-time events (new candidate, stage moved, hired) to
a URL you define. Shipping soon.
Integrations FAQ
What can I do via Zapier or Make?
Both ship as native TalentGleam apps with full triggers, actions, and
searches. Triggers fire a Zap or scenario when something
happens in TalentGleam (new candidate, stage changed, hired). Actions
let an external tool write back to TalentGleam (create a candidate,
add a tag, change a stage). Searches let a Zap or scenario
look up data in TalentGleam by attribute (find a candidate by email,
find a role by department).
How do I authenticate against the public API?
Each user generates a personal access token from their
workspace settings. The token passes in the Authorization
header on every request. Tokens are scoped to the user's
permissions in TalentGleam, so an API call can't read or write data
the user couldn't access through the UI.
When will webhooks be available?
Outbound webhooks are shipping soon. They'll post events (new
candidate, stage moved, hired, rejected, and more) to a
customer-defined URL, useful when you want push-based
integration instead of polling. Talk to us if you want early
access while we finalise the event catalogue.
Are there native integrations with HRIS, Slack, or BI
tools, without going through Zapier?
Not today. Every third-party connection goes through one of
four surfaces: the Zapier app, the Make app, the public REST
API, or (soon) outbound webhooks. The trade-off: Zapier and
Make between them cover 9,000+ apps — far more than any ATS
native marketplace. Most customers wire up their HRIS
(BambooHR, Personio, HiBob), Slack notifications, and BI
exports via Zapier or Make in under an hour, no IT required.
Where's the API documentation?
Linked from your workspace settings under Integrations once
you generate a personal access token. The doc covers every
endpoint, request and response shapes, and the auth contract.
