Roadmap Feature: Webhooks are currently in development. This documentation describes the planned implementation.
Overview
Webhooks allow you to receive real-time HTTP notifications when events occur in Day Copilot, eliminating the need for polling. Benefits:- Real-time updates
- Reduced API calls
- Lower latency
- Event-driven architecture
Supported Events (Planned)
Task Events
task.created- New task createdtask.updated- Task modifiedtask.deleted- Task removedtask.completed- Task marked as completetask.assigned- Task assigned to usertask.comment_added- Comment added to task
Event Events
event.created- New calendar event createdevent.updated- Event modifiedevent.deleted- Event removedevent.attendee_added- Attendee addedevent.rsvp_changed- RSVP status updated
Context Events
context.created- New context createdcontext.shared- Context shared with usercontext.updated- Context modified
Webhook Setup
1. Create Webhook Endpoint
Your endpoint must:- Accept POST requests
- Return 200 status quickly (under 5 seconds)
- Verify webhook signature (security)
- Process events asynchronously
2. Register Webhook
3. Verify Webhook
Day Copilot will send a verification request:Webhook Payload Format
All webhook events follow this structure:id: Unique event identifier (for deduplication)type: Event typecreated_at: When event occurreddata: Event-specific dataactor: User who triggered the event
Event Examples
task.created
task.updated
task.assigned
Security
Signature Verification
Day Copilot signs all webhook requests:Best Practices
Always Verify Signatures
Always Verify Signatures
Never process webhooks without verifying signatures. This prevents spoofing and ensures authenticity.
Respond Quickly
Respond Quickly
Acknowledge webhook receipt within 5 seconds. Process events asynchronously to avoid timeouts.
Handle Duplicate Events
Handle Duplicate Events
Use event IDs for deduplication:
Implement Retries
Implement Retries
If your endpoint fails, Day Copilot will retry with exponential backoff:
- Retry 1: After 1 minute
- Retry 2: After 5 minutes
- Retry 3: After 15 minutes
- Retry 4: After 1 hour
- Retry 5: After 6 hours (final attempt)
Managing Webhooks
List Webhooks
Update Webhook
Delete Webhook
Test Webhook
Manually trigger a test event:Webhook Logs
View delivery logs and retry history:Common Patterns
Sync to External System
Notification System
Analytics Tracking
Testing Locally
Use ngrok for Local Development
Mock Webhook Events
Current Status
Webhooks are planned for release in Q1 2026. Until then, use polling:Next Steps
First API Call
Get started with the API
Error Handling
Handle webhook delivery failures
Authentication
Secure your webhook endpoint
API Reference
Explore all endpoints
Feedback
We’re designing webhooks based on developer feedback. Let us know what events you need:Request Webhook Features
Share your webhook requirements with our API team