Internal code reference

Integrating with the platform vs. building on the platform

Contributor API vs Developer API

We make a clear distinction between the Developer API and the Contributor API, because it clarifies a fundamental difference in audience and purpose:

• Developer APIs focus on consumption and integration patterns, emphasizing stability, usability, and external use cases

• Contributor APIs document implementation details, internal architecture decisions, and modification workflows that enable effective contribution to the codebase.

Clearly, every software system has a "Contributor API", so it is unfortunate there is no standard industry term for this. The term "Contributor API" is especially well-suited to an open-source context where internal team members are indeed contributors, and the term aligns perfectly with established terminology for collaboration in both public and private GitHub repositories.

By adopting this convention, we make it immediately clear whether documentation is intended for those integrating with the system versus those building on the system. In turn, this helps reduce confusion and ensures contributors can easily locate the technical depth they need for internal development work.

Contributor API

Internal interface for team members modifying and maintaining the system

Developer API

External public interface for developers and integrators extending the system