How was the API structured?

Short explanation:

API structure describes how a request moves from the client through validation and access checks to business logic and persistence. It also includes resource names, error contracts and how responsibilities are separated. A real endpoint example makes the structure easier to understand than a folder list.

Key points:

• “Requests went through [actual validation/auth flow] to [controller/service/data layer].”

• Give one real endpoint, input and response example.

• Walk through method/path, accepted fields, caller permissions, service operation and expected response.

Interview point:

• Explain why the separation helped testing or changes, not only that controllers and services existed.