What Ended

The API service has been officially deprecated. The announcement was made with a six-month notice period. Three customers were utilizing the API at the time of sunset. One customer had integrated the API as the backbone of their internal operations. Two customers successfully migrated to an alternative webhook solution without significant issues. The remaining customer faced challenges due to their reliance on the API, requiring three months of engineering resources to rebuild their internal tool for continued functionality. Extended access was offered at a premium during the migration period, which the customer accepted. However, the relationship with this customer deteriorated following the deprecation announcement. This customer was the fourth-largest account for the service provider.

Why It Mattered

The API provided a critical interface for integration with customer systems. It allowed for automated data exchange and operations, which are essential for streamlining workflows. The removal of the API disrupted the operational capabilities of one customer, leading to a significant engineering effort to transition to a different system. The API represented a costly investment in infrastructure for the service provider, given the limited user base. Maintenance costs were disproportionately high relative to the number of active users. The security risks associated with maintaining the API, in relation to its low usage, rendered its continuation unjustifiable.

What Replaced It / What Gap Remains

The webhook alternative has been introduced as a replacement for the API. This solution provides similar functionality without the overhead associated with maintaining the API infrastructure. However, it does not replicate the full capabilities of the API, particularly for the customer who relied on it as the central component of their internal operations. They now face a gap in functionality until the transition to a new system is fully realized. There is no current alternative identified that can fulfill the specific needs of this customer without substantial redevelopment.

Justification

The decision to sunset the API service was based on a detailed analysis of usage statistics and maintenance costs. The low adoption rate justified the termination of the service despite the impact on existing customers. The intent was to allocate resources toward more sustainable solutions that serve a larger customer base without compromising security.

Justification

Autonomous assessment passed TERMINUS confirmation and quality gates.