Update: Softbook v.2.0.4
In this release, we focused on making access management more convenient, improving payment integration reliability, and expanding API capabilities.
🔑 Bulk access management
Now you can open or close access to courses and lessons for specific student groups in just one action. Less routine — more control and scalability.
📩 New system email
Students now automatically receive a notification when their subscription ends — helping avoid confusion and encouraging them to renew access.
⚙️ Webhooks
Three new triggers have been added:
- Subscription cancelled by student
- Subscription renewed manually
- Subscription renewed automatically
This gives you even more control over the subscription lifecycle and lets you trigger automations based on each event.
💳 Improved payment logic with WayForPay
If a payment fails, students will no longer be redirected to the success page.
You can now set a custom page for failed payments in the product settings.
📡 API updates
The add contact method now supports custom fields — pass more data and automate more processes.
The add student method no longer returns an error if the student already exists in the school — instead, they are simply enrolled in the new courses specified in the request. Simple and safe.
📝 Fixes and improvements
- Fixed the display of multi-level lists in the homework editor
- Improved filter behavior and UI stability
Frequently asked questions
What does bulk access management do in Softbook 2.0.4?
Administrators can open or close access to selected courses and lessons for an entire student group in one action. This replaces repeated changes on individual student accounts, reduces routine work, and makes access management easier to scale when a school runs several programs or serves large cohorts.
Which subscription notifications and webhook events were added?
Students now receive an automatic system email when a subscription ends, reducing confusion and prompting timely renewal. Three webhook triggers cover a subscription cancelled by the student, renewed manually, or renewed automatically. Schools can connect each lifecycle event to a suitable notification, CRM update, or other automated process.
How was WayForPay behavior improved for failed payments?
A failed WayForPay payment no longer sends the student to the success page. In product settings, the school can choose a separate page for unsuccessful payments. This gives the buyer accurate status information and lets the school provide relevant instructions, another payment attempt, or support instead of showing a misleading confirmation.
What changed in the Softbook API in version 2.0.4?
The add contact method can now accept custom fields, allowing integrations to transfer more information and automate additional workflows. The add student method also handles existing students safely: instead of returning an error, it enrolls that account in the new courses included in the request.
Which interface fixes are included in Softbook 2.0.4?
The release corrects the display of multilevel lists in the homework editor, so nested instructions are easier to read and format. It also improves filter behavior and overall interface stability. These fixes accompany the larger access, subscription, payment, webhook, and API changes in the same update.
