Recently we shared with the TCF Product Forum the learnings from the recent consultation with you about a proposal to build a suite of new Fibre Ordering APIs to eventually replace B2B. 

The timings have slightly changed

The planned commencement of the initiative, and design and build of the first API has been delayed to a more realistic start date of January 2023. We will continue to keep you updated on progress towards this date, and will be creating a dedicated project webpage for you soon.

We are seeking participants to help us with the design

There are many pieces of the puzzle to consider across such a significant initiative, our broader API programme and supporting ecosystem. As proposed, we plan to share incremental topics for your input throughout a series of ‘design loops’. The loops will run slightly ahead of the build schedule.  

The first two topics will be Versioning and Notifications/Webhooks which we aim to facilitate during October.  

What's involved? 

Participation will be a low-effort commitment, ideally over the long term. The aim is that most of the same participants will support us throughout the design, build, test, and onboarding of all the new API. 

Every 1-2 months, we will share a concept, prototype, or new API spec, facilitated with a 1-2 hour virtual call to convey the idea and talk it through with Q&A. We will also use a dedicated MS Teams channel to communicate upcoming design topics and keep the design conversation going with our technical team on a particular case without needing more meetings. 

Who are the right people to help us? 

Spaces will be limited to ensure the timing, discussion, and cadence remain an effective use of everyone’s time. Should the spaces be oversubscribed, the experience criteria below may be used to limit numbers. 

We are seeking technical people from across the spectrum of our customer base, including those already connected to our B2B, those who haven’t connected yet but want to, and our LFC community. 

Participants will need the following experience: 

Essential: 

• Experience in working with RESTful APIs 
• Performing a role like one of the below: 
• Senior Architect 
• Lead developer  
• Technical lead 
• QA Tester 
• Change Manager 
• An understanding of core fibre business processes  

Nice to have: 

• Understanding of the TMForum Open API  
• Experience in the development of APIs 
• Experience in publishing APIs for consumption externally 

Action 

Please email to digital@chorus.co.nz by close of business 30 September 2022 with your nominated attendee/s including: 

• The name of the participant 
• The role they perform in your organisation 
• Their email address 

We will respond soon afterwards to confirm attendees, share our suggested terms of engagement for collaboration, and details of the first design topics.