Webhooks let Stardex notify an external service as soon as supported recruiting records change. Administrators manage endpoints and event subscriptions from an in-app portal, then inspect deliveries and replay failures without rebuilding the originating event.

What you can do

Recruiting event coverage — Subscribe to candidate, person, job, company, client contact, deal, and meeting-recording events.

Endpoint management — Add delivery URLs and choose exactly which event families each endpoint should receive.

Delivery visibility — Inspect attempts and payload history when diagnosing an integration.

Retries and replay — Recover from temporary endpoint failures without asking users to repeat the original recruiting action.

Set up in three steps

Prepare an HTTPS endpoint — Build a handler that can verify, process, and safely deduplicate Stardex events.

Configure subscriptions — Add the endpoint in the webhook portal and select the relevant event types.

Test failure handling — Confirm successful delivery, retry behavior, and replay before relying on the event in production.

Built for the way search firms work

Engineering teams keep internal systems current after ATS changes.

Operations teams trigger downstream reporting when jobs or candidates move.

Data teams capture event history for analytics pipelines.

Product teams react when meeting recordings and summaries become available.

Frequently asked questions

Which events are available?

Supported families include candidate, person, job, company, client contact, deal, and completed meeting-recording events.

Which events are available?

Supported families include candidate, person, job, company, client contact, deal, and completed meeting-recording events.

Can failed deliveries be replayed?

Yes. The portal supports inspecting deliveries and replaying failures.

Can failed deliveries be replayed?

Yes. The portal supports inspecting deliveries and replaying failures.

Should consumers deduplicate events?

Yes. Production endpoints should process retries idempotently so the same event cannot create duplicate work.

Should consumers deduplicate events?

Yes. Production endpoints should process retries idempotently so the same event cannot create duplicate work.

Do webhooks replace the API?

No. Webhooks announce changes; the REST API handles broader record reads and writes.

Do webhooks replace the API?

No. Webhooks announce changes; the REST API handles broader record reads and writes.

Related integrations

REST API

Zapier

MCP

Connect Webhooks to your Stardex workflow

See how Stardex connects your team’s recruiting workflow without adding manual admin.

Book a demo