Webhooks
Webhooks let you subscribe to events from your LLMTune workspace for automation and monitoring. Receive real-time notifications when training jobs complete, deployments change, or usage thresholds are reached.Supported Events
| Event | Trigger |
|---|---|
training.started | A fine-tuning job enters the running state |
training.completed | A job finishes successfully |
training.failed | A job fails or is cancelled |
model.deployed | A model is promoted to an endpoint |
deployment.created | A new endpoint becomes active |
deployment.paused | An endpoint is paused |
deployment.deleted | An endpoint is permanently removed |
usage.threshold_reached | Usage metrics cross configured thresholds |
Register a Webhook
- Navigate to Webhooks in the dashboard.
- Click Create Webhook.
- Provide:
- Target URL (HTTPS recommended)
- Secret for signature validation (optional but recommended)
- Events to subscribe to (select one or more)
- Save and test using the Send Test Event button.
Payload Format
LLMTune sends POST requests to your webhook URL with the following payload structure:Training Events
Deployment Events
Signature Verification
LLMTune signs webhook payloads using HMAC SHA-256. Verify signatures using your shared secret:X-LLMTune-Signature header.
Response Handling
- Respond with
2xxstatus codes to acknowledge receipt - LLMTune retries failed deliveries with exponential backoff
- Maximum retry attempts: 5
- Timeout: 30 seconds per request
Best Practices
- Use unique secrets per webhook endpoint
- Acknowledge quickly – Respond with 200 OK immediately, then process asynchronously
- Log received events for debugging and auditing
- Validate signatures to ensure requests are from LLMTune
- Handle idempotency – Events may be delivered multiple times; use event IDs to deduplicate
- Monitor webhook health – Set up alerts if webhooks fail repeatedly
Testing Webhooks
- Use the Send Test Event button in the webhook configuration
- Test your endpoint locally using tools like ngrok or localtunnel
- Verify your endpoint handles all subscribed event types
Troubleshooting
- Webhook not receiving events: Check that your endpoint is publicly accessible (HTTPS) and returns 2xx responses
- Signature verification fails: Ensure you’re using the correct secret and computing the signature correctly
- Events delayed: Check your endpoint response time; slow responses may cause retries
- Missing events: Review webhook logs in the dashboard to see delivery status
Next Steps
- Learn about Deployment to understand when deployment events fire
- Read the Fine-Tuning Guide to see training event triggers
- Check the API documentation for programmatic webhook management