Skip to main content
POST
Fire Webhook Trigger

Fire Webhook Trigger

Trigger an automation via webhook. The webhook payload will be mapped to application/candidate fields based on the trigger’s field mapping configuration.

Endpoints

Authentication

[!NOTE] This endpoint is authenticated via the unique webhook URL (public_id) and does not require an API key.

Path Parameters

Request Body (POST)

The request body structure depends on the field mapping configuration of the webhook trigger.

Example Request

Responses

202: Accepted

Webhook received and queued for async processing.

400: Bad Request

Automation inactive, empty payload, or validation error.

404: Not Found

Webhook trigger not found.

409: Conflict

Idempotency conflict during concurrent request processing.

429: Too Many Requests

Rate limit exceeded.

503: Service Unavailable

Service temporarily unavailable (rate limiting infrastructure down).

Notes

  • The automation executes asynchronously — the response confirms the trigger was received
  • Both GET and POST methods are supported
  • The webhook payload fields should match the automation’s field mapping configuration