What is an API (deep)
Reviewing APIs as request/response contracts.
Difficulty 2/5
Short
Plain English
Reviewing APIs as request/response contracts. Picture it like this: A menu and an order slip. In the apps you ship (Agentify, wedding portals, CRM), you will bump into this on almost every screen — name it clearly when you prompt your coding agent.
Analogy
A menu and an order slip.
Go deeper
Reviewing APIs as request/response contracts.
Common mistakes
- Letting the AI rename this concept three different ways in one PR.
- Building UI before you can say what is stored and who can change it.
AI-agent trap
Agents may invent jargon here. Ask them to explain the concept in plain English first, then map it to your schema and one real screen.
Summary
Reviewing APIs as request/response contracts. A menu and an order slip. Ask yourself: where does this live in the database, which function changes it, and which screen shows it?
Confidence: