Skip to main content
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 created
  • task.updated - Task modified
  • task.deleted - Task removed
  • task.completed - Task marked as complete
  • task.assigned - Task assigned to user
  • task.comment_added - Comment added to task

Event Events

  • event.created - New calendar event created
  • event.updated - Event modified
  • event.deleted - Event removed
  • event.attendee_added - Attendee added
  • event.rsvp_changed - RSVP status updated

Context Events

  • context.created - New context created
  • context.shared - Context shared with user
  • context.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

Response:

3. Verify Webhook

Day Copilot will send a verification request:
Respond with:

Webhook Payload Format

All webhook events follow this structure:
Fields:
  • id: Unique event identifier (for deduplication)
  • type: Event type
  • created_at: When event occurred
  • data: Event-specific data
  • actor: User who triggered the event

Event Examples

task.created

task.updated

task.assigned

Security

Signature Verification

Day Copilot signs all webhook requests:
Verify signature:

Best Practices

Never process webhooks without verifying signatures. This prevents spoofing and ensures authenticity.
Acknowledge webhook receipt within 5 seconds. Process events asynchronously to avoid timeouts.
Use event IDs for deduplication:
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:
Response:

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