Articles on: Integrations

Use 100Hires Webhooks for Custom Integrations

Use 100Hires Webhooks for Custom Integrations


Webhooks let your systems react to hiring events in 100Hires without polling the API on a schedule.


The 100Hires OpenAPI specification is the source of truth for the current webhook endpoints, request fields, and response schemas:


https://api.100hires.com/v2/openapi.json


Get an API key


Go to Settings > Integrations and find the Personal API key section for the Developer API. API keys require account verification.


Personal API key card in Settings > Integrations with Generate and API documentation controls


Use the key in the Authorization: Bearer header for API requests.


Company-level vs per-job webhooks


100Hires supports two webhook scopes:


  • Company-level webhooks: configured under company webhook endpoints. Use them for account-wide integrations such as BI dashboards or HRIS sync.
  • Job-level webhooks: configured under job webhook endpoints. Use them when an integration is tied to one specific job.


Current API endpoints


Based on the current OpenAPI spec, webhook management endpoints include:


GET    /companies/{id}/webhooks
POST /companies/{id}/webhooks
GET /companies/{id}/webhooks/{webhook_id}
DELETE /companies/{id}/webhooks/{webhook_id}

GET /jobs/{id}/webhooks
POST /jobs/{id}/webhooks
GET /jobs/{id}/webhooks/{webhook_id}
DELETE /jobs/{id}/webhooks/{webhook_id}


Creating a webhook


The current WebhookCreateRequest requires a single field:


{
"url": "https://hooks.example.com/100hires"
}


The URL must be HTTPS. Do not add event-type fields unless the OpenAPI spec has been updated to support them.


Supported events and payloads


For the current event names and payload shape, use the OpenAPI spec and test against a webhook inspector endpoint before connecting production systems. Event and payload details can change as the API evolves.


Common use cases


  • Sync new hires from 100Hires into your HRIS.
  • Push stage changes to a custom dashboard.
  • Trigger a downstream workflow when applications move through the pipeline.
  • Mirror candidate or application changes to an internal CRM.


Reliability and security


Build your handler defensively: return success only after processing, make processing idempotent, and log received payloads during testing. For current retry behavior, signing, or IP allowlisting details, check the OpenAPI spec or contact support before relying on a specific production guarantee.



These screenshots show the 100Hires areas used in this workflow.


Settings > Integrations scrolled to the Personal API key section and AI Assistants (MCP) section with MCP Server URL and Quick setup dropdow


Zapier field mapping step for sending 100Hires data to another app

Updated on: 18/06/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!