Webhooks
Webhooks allow your systems to receive real-time notifications when events occur in Reading Steps.Webhooks are currently in beta. Contact support@helpdesk.readingsteps.uk to request access.
Overview
When enabled, Reading Steps sends HTTP POST requests to your specified endpoint whenever certain events occur.Setting up webhooks
- Go to Admin Panel > Integrations
- Click Webhooks
- Enter your endpoint URL
- Select which events to subscribe to
- Save and test the connection
Webhook payload
All webhooks are sent as JSON with this structure:Available events
Student events
| Event | Description |
|---|---|
student.created | New student added |
student.updated | Student details changed |
student.archived | Student archived |
student.reading_completed | Student finished a reading session |
student.level_changed | Student’s reading level changed |
Class events
| Event | Description |
|---|---|
class.created | New class created |
class.updated | Class details changed |
class.archived | Class archived |
Assessment events
| Event | Description |
|---|---|
assessment.completed | Student completed an assessment |
assessment.level_assigned | Reading level assigned from assessment |
Event payloads
student.reading_completed
student.level_changed
assessment.completed
Security
Verifying webhooks
Each webhook includes a signature header for verification:Webhook secret
Your webhook secret is displayed when you create the webhook endpoint. Store it securely and use it to verify incoming requests.Retry policy
If your endpoint returns a non-2xx status code, Reading Steps retries:| Attempt | Delay |
|---|---|
| 1 | Immediate |
| 2 | 1 minute |
| 3 | 5 minutes |
| 4 | 30 minutes |
| 5 | 2 hours |
Best practices
- Respond quickly - Return a 200 status within 5 seconds
- Process asynchronously - Queue webhook data for background processing
- Handle duplicates - Use the event ID to deduplicate
- Verify signatures - Always verify the webhook signature
- Monitor failures - Set up alerts for webhook failures