Sprint Duration: December 15 – December 30, 2025
Release Date to Production: Thursday, February 5th, 2026
Quick Peek – What We Delivered
Sprint 2.1.1 focused on a major milestone: the release of NumHub’s first set of webhooks to support real-time BCID application and display identity updates. We also continued enhancing our vetting operations and resolved UAT-identified issues before production.
Detailed Changes
1. New Webhooks for BCID Applications and Display Identity Events
We’re excited to introduce the first three webhooks available in the platform. These enable real-time alerts when key events happen during BCID onboarding and display identity management. You no longer need to poll the API — instead, receive immediate updates as soon as changes occur.
A. BCID Webhook: Notify on Application Submission
Triggers when a BCID application is submitted. Payload includes:
EID and Client ID
Status (e.g., “Pending Review”)
Submission timestamp
Last modified date
All seven steps of the application and their submitted details
Why it matters:
Use this webhook to automatically track when your enterprise clients complete the BCID submission.
B. BCID Webhook: Notify on Vetting Updates
Triggers whenever there’s a change in vetting status. Possible scenarios:
Approved – All steps marked as Passed
Flagged – One or more steps need revision
Rejected – At least one step marked as Rejected
Payload includes:
EID and Client ID
Updated status (e.g., “Approved”, “Flagged”, “Rejected”)
Step-by-step vetting results
Comments explaining flag or rejection reasons
Why it matters:
Get alerted as soon as your application status changes — and know exactly what to fix, if needed.
C. Display Identity Webhook: Creation and Change Request Events
Triggers under multiple display identity scenarios:
-
New Display Identity Created
Fires when a BCID application is approved and a display identity is activated
Includes Display Identity ID, EID, Client ID, and brand asset details
-
Change Request Submitted
Triggers when you or an enterprise submits a modification request (e.g., new number, updated logo)
Payload includes the change type and original display info
-
Change Request Approved
Notifies you that a requested change has been approved
Includes the updated display identity data
-
Change Request Rejected
Notifies you if the requested change was rejected
Confirms that the original display identity remains active
Why it matters:
Track changes to your brand displays and receive approvals or rejections in real time, without having to check the portal manually.
2. Enhancements to Internal Vetting Queue
We made internal improvements to the backend vetting queue used by our CX and Operations team to review BCID applications.
Enhancements include:
Better tracking of application status history
Improved internal interface for viewing step-by-step changes
Additional logging to support faster resolution and transparency
3. Bug Fixes in UAT Environment
Before deploying the previous sprint’s work to production, we resolved several bugs found during UAT testing. Fixes addressed issues related to display identity processing, application history rendering, and edge-case webhook payload generation.
These fixes help ensure that all new webhook and vetting functionality behaves as expected when released.
Why It Matters to You
Real-Time Integration: With webhooks now live, you can automate internal workflows, respond faster to application changes, and improve client communication.
Clearer Display Management: Know exactly when display identities are created, modified, approved, or rejected — instantly.
Improved Internal Vetting = Faster Turnaround: Backend improvements support quicker reviews and smoother flag resolution.
More Stable Releases: Addressing bugs early in UAT keeps your production experience seamless and reliable.
Questions or Feedback?
As always, we welcome your thoughts and suggestions. Contact Daniela Villamar at dvillamar@numhub.com for any questions, ideas, or support.
We’re excited to bring webhooks to life — and we’re just getting started.
Comments
0 comments
Please sign in to leave a comment.