Architecture comprising an application programming interface (API) for representing and accessing various configuration data related to an enterprise messaging communications system. The API includes three classes for accessing stored configuration data related to enterprise recipients that can receive messages (e.g., e-mail), one or more servers that facilitate messaging communications of the enterprise, and a messaging connector for proper flow of message internal and external to the enterprise. By encapsulating these sets of configuration data into distinct classes, business logic that interprets these classes can be centralized thereby avoiding duplicate and incompatible logic.