Technical for PMs · Easy
How would you explain what an API is to a non-technical stakeholder?
Short answer
An API is an agreed way for one piece of software to request information or actions from another, without needing to know how the other works inside. A useful analogy is a restaurant menu: you choose from defined options and get a predictable result. Then make it concrete with an example from your own product, such as checking payment status.
Detailed answer
A clear explanation in three layers
- Definition: an application programming interface is a contract. It says what you can ask for, how to ask and what you will get back.
- Analogy: a menu at a restaurant. You do not walk into the kitchen; you order from a list, and the kitchen returns your dish. If you order something not on the menu, you get an error.
- Concrete example from your product: "When a customer pays, our app asks the payment provider's API, 'Did this payment succeed?' and gets back a yes, no or pending."
Why it matters to stakeholders
- Partnerships: integrating with another company usually means using their API, so timelines depend on its quality and documentation.
- Speed: good internal APIs let teams build features without waiting on each other.
- Risk: when an external API is slow or down, features depending on it may fail, so we need fallbacks.
- Business models: some companies sell access to their APIs, often priced per request.
Worked example
A sales leader asks why integrating with a new accounting tool will take six weeks. You explain that the tool's API does not offer some data we need, so engineers must work around it, and that we need to handle errors, rate limits and testing.
Common pitfalls
- Over-technical answers mentioning REST, JSON and status codes without context.
- Analogies with no link back to the product.
- Implying APIs are "plug and play" with no effort.