An organization is struggling to ensure that their legacy systems meet rapidly changing IT needs. Why should the organization use application programming interfaces (APIs)?

APIs expose defined interfaces and operations, not all underlying data; they are specifically designed to control access, not to give third parties unrestricted ability to modify data.

APIs are an integration strategy that enables connectivity to existing systems; they do not re-architect or replace the legacy applications themselves.

APIs create a stable abstraction layer over legacy systems, allowing the underlying implementation to remain unchanged while new consumers and integrations can be added over time. This decoupling gives organizations the flexibility to evolve their IT ecosystem incrementally and respond to changing needs without costly rewrites.

A pay-as-you-go pricing model is a characteristic of cloud infrastructure billing, not a function or benefit of APIs.