Automatic Logging: All webhook deliveries sent to your configured webhook URL are automatically logged. You don’t need to configure anything - logs are captured automatically for monitoring and debugging purposes.
Accessing Webhook Logs
Webhook Logs are accessible through the TapTalent dashboard interface. Follow these steps to view your webhook logs:Step 1: Navigate to Webhook Logs
- Log in to your TapTalent Dashboard
- Navigate to Account Settings > Developers > Webhook Logs
Step 2: View Your Logs
The Webhook Logs page displays a table of all webhook deliveries with the following information:- Timestamp: Date and time when the webhook was sent
- Event: The event type that triggered the webhook (e.g.,
resume.bulk_upload_parse.started) - Status: Delivery status (Pending, Success, Failed, Retrying)
- Response Code: HTTP status code received from your webhook endpoint (200, 400, 500, etc.)
- Retry Count: Number of retry attempts made for failed deliveries
Step 3: Filter Your Logs
Use the filter options at the top of the page to narrow down your search: Filter by Status Code:- All Status: View all webhook deliveries
- 2xx - Success: View only successful deliveries (200-299)
- 3xx - Redirect: View redirect responses (300-399)
- 4xx - Client Error: View client errors (400-499)
- 5xx - Server Error: View server errors (500-599)
- Filter by specific webhook events:
resume.bulk_upload_parse.started- Resume bulk upload parsing startedresume.bulk_upload_parse.completed- Resume bulk upload parsing completedresume.bulk_upload_parse.failed- Resume bulk upload parsing failed
- Select a date range using the calendar picker to view logs from a specific time period
Step 4: View Log Details
Click on any log entry in the table to view detailed information: Webhook Details:- Event type that triggered the webhook
- Webhook payload (the data sent to your endpoint)
- Request URL (your configured webhook endpoint)
- HTTP method (always POST)
- Delivery status (Pending, Success, Failed, Retrying)
- Response status code from your endpoint
- Response payload received from your endpoint
- Number of retry attempts
- Timestamps for when the webhook was sent and when delivery completed
- Company ID and Client ID
- Timestamps for when the log was created and updated
Understanding Log Data
What Gets Logged
Every webhook delivery automatically captures:| Information | Description |
|---|---|
| Event Type | The webhook event that triggered the delivery (e.g., resume.bulk_upload_parse.started) |
| Request URL | Your configured webhook endpoint URL |
| Request Payload | The JSON payload sent to your webhook endpoint |
| Status | Delivery status: Pending, Success, Failed, or Retrying |
| Response Status Code | HTTP status code returned by your webhook endpoint |
| Response Payload | Response body returned by your webhook endpoint |
| Retry Count | Number of retry attempts made for failed deliveries |
| Timestamp | When the webhook was sent |
Delivery Statuses
Webhook deliveries can have the following statuses:- Pending: Webhook is queued for delivery but hasn’t been sent yet
- Success: Webhook was successfully delivered and your endpoint returned a 2xx status code
- Failed: Webhook delivery failed after all retry attempts were exhausted
- Retrying: Webhook delivery failed and is being retried
Retry Policy
When a webhook delivery fails, TapTalent automatically retries the delivery:- Retries are attempted with exponential backoff
- Failed deliveries are retried multiple times before being marked as failed
- You can monitor retry attempts in the webhook logs
Use Cases
Debugging Webhook Issues
When your webhook endpoint isn’t receiving events or responding correctly:- Filter by Failed Status: Use the status filter to show only failed deliveries
- Review Failed Requests: Click on failed entries to see the error response from your endpoint
- Check Response Codes: Identify patterns in error responses (4xx vs 5xx)
- Monitor Retry Attempts: See how many times TapTalent retried failed deliveries
Monitoring Webhook Delivery
Track how your webhook integration is performing:- View Success Rates: Filter by status codes to see success vs failure ratios
- Monitor Event Types: See which events are being sent most frequently
- Track Delivery Times: Review timestamps to understand delivery latency
- Identify Endpoint Issues: Look for patterns in failed deliveries
Auditing Webhook Activity
Maintain records of all webhook deliveries:- Date Range Filtering: Use the date picker to view logs from specific time periods
- Review All Deliveries: See a complete history of all webhooks sent to your endpoint
- Track Event Patterns: Monitor which events are triggered and when
- Compliance: Use logs for audit trails and compliance reporting
Best Practices
Regular Monitoring
- Check logs regularly to catch delivery failures early
- Filter by failed status to focus on issues
- Monitor retry attempts to identify persistent endpoint problems
Debugging Workflow
- Identify the Issue: Filter logs by failed status or specific event types
- Review Details: Click on failed entries to see full request/response data
- Check Your Endpoint: Verify your webhook endpoint is accessible and responding correctly
- Review Response Codes: Understand what status codes your endpoint is returning
- Fix and Verify: Make corrections to your endpoint and check new deliveries to confirm the fix
Endpoint Health
- Monitor success rates: Track the percentage of successful deliveries
- Review response times: Check if your endpoint is responding quickly enough
- Handle retries: Ensure your endpoint can handle duplicate webhook deliveries (idempotency)
Tips
Finding Specific Webhooks
- Use date range filter to narrow down to a specific time period
- Filter by event type to see only specific webhook events
- Filter by status code to focus on errors or successful deliveries
- Combine filters for more precise searches
Understanding Status Codes
- 2xx (200-299): Success - Your endpoint received and processed the webhook successfully
- 3xx (300-399): Redirect - Your endpoint redirected the request
- 4xx (400-499): Client Error - Issue with your endpoint (invalid request format, authentication, etc.)
- 5xx (500-599): Server Error - Issue on your endpoint’s side
Webhook Payloads
- Webhook payloads contain the event data sent to your endpoint
- Review payloads to understand what data is being sent
- Ensure your endpoint can parse and handle the payload format
Next Steps
- Review Webhooks Overview for webhook setup and configuration
- Explore other API endpoints
- Review Integration Notes for best practices
.png?fit=max&auto=format&n=lKy84_BssSCy2hcz&q=85&s=ac7c949427cc2893306f6036415f087e)