The Performance Dashboard API provides aggregated performance metrics and statistics for the GOV.UK Notify platform.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/alphagov/notifications-api/llms.txt
Use this file to discover all available pages before exploring further.
Base URL
Authentication
All endpoints require admin authentication.Endpoints
Get Performance Dashboard
Retrieve comprehensive performance statistics for the platform, including total notifications, processing times, and live services.Parameters
Start date in YYYY-MM-DD format. Defaults to today.
End date in YYYY-MM-DD format. Defaults to today.
Response
Response Fields
Top-level Statistics
total_notifications- Total number of notifications sent across all timeemail_notifications- Total emails sent across all timesms_notifications- Total SMS sent across all timeletter_notifications- Total letters sent across all timelive_service_count- Number of currently live services on the platform
Notifications by Type Array
Daily breakdown of notifications within the specified date range:date- Date in YYYY-MM-DD format (BST timezone)emails- Number of emails sent on this datesms- Number of SMS sent on this dateletters- Number of letters sent on this date
Processing Time Array
Daily processing time performance metrics:date- Date in YYYY-MM-DD formatpercentage_under_10_seconds- Percentage of notifications processed within 10 seconds
The 10-second threshold is a key performance indicator for the platform. It measures how quickly notifications are accepted and queued for delivery.
Services Using Notify Array
List of all live services currently using the platform:service_id- UUID of the serviceservice_name- Name of the serviceorganisation_id- UUID of the parent organisation (or null)organisation_name- Name of the parent organisation (or null)
Data Aggregation
All-Time Totals
Thetotal_notifications, email_notifications, sms_notifications, and letter_notifications fields represent cumulative totals across the platform’s entire history, regardless of the date range specified.
Date Range Data
Thenotifications_by_type and processing_time arrays are filtered to the specified date range:
- If no dates are provided, defaults to today’s data
- Data is aggregated by date in BST (British Summer Time)
- Each date includes all notifications processed on that day
Live Services
Theservices_using_notify array includes all services with a status of “live”:
- Includes both services with and without parent organisations
- Ordered by service name
- Includes only active, production-ready services
Use Cases
Platform Health Dashboard
Monitor overall platform performance:Weekly Performance Report
Generate a weekly performance report:Monthly Trends Analysis
Analyze monthly processing time trends:Performance Metrics
Processing Time SLA
The platform aims to process 99.95% of notifications within 10 seconds. This measures:- Time from API request received to notification queued for sending
- Does not include actual delivery time (varies by channel and provider)
- Excludes scheduled notifications (measured from scheduled time)
Notification Volume Trends
Daily volumes help identify:- Peak usage periods
- Growth trends
- Seasonal patterns
- Unusual spikes or drops that may indicate issues
Service Growth
Thelive_service_count tracks platform adoption:
- Services that have completed onboarding
- Services actively sending notifications
- Excludes trial and inactive services
Notes
- All statistics are calculated from the
ft_notification_statusfact table - Processing times are calculated from the
ft_processing_timefact table - Live services are queried in real-time from the
servicestable - All dates use YYYY-MM-DD format
- Times are referenced in BST (British Summer Time) for date boundaries
- Historical data is available from the platform’s launch