Fleshing out API details
After identifying the resources, you work on the details of each API, that is, what is the input, the validation rules, the output, and status codes. You also need to specify the naming conventions and the data format. Once the details are fleshed out, you shouldn't go straight into the implementation phase. Instead, you should ask the developers of the clients of the API for feedback in order to see what you might have missed, and what further adjustments are required. One thing you should probably avoid is factoring in how the UI of the clients works into the API design consideration. How users interact with the UI of the clients of your API is irrelevant. You want to make the API generic so that it can be used ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access