API response
Status + headers + body.
Difficulty 2/5
Short
Plain English
Status + headers + body. Picture it like this: The plate that comes back. 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
The plate that comes back.
Go deeper
Status + headers + body.
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
Status + headers + body. The plate that comes back. Ask yourself: where does this live in the database, which function changes it, and which screen shows it?
Confidence: