. . . . . . . . . 317
Learn From and Emulate Other APIs. . . . . . . . . . . . . . . . . . . . . . . . . . 318
Keep in Mind Your Audiences for the API . . . . . . . . . . . . . . . . . . . . . . 318
Make Your API Easy to Learn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Test the Usability of Your API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Build a Granular, Loosely Coupled Architecture So That
Creating an API Serves You As Much As It Does Others. . . . . . . 319
Embrace REST But Also Support SOAP and XML-RPC
If You Can . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
?– CONTENTS xiv
Consider Using the Atom Publishing Protocol As a Specific
Instantiation of REST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Encourage the Development of API Kits: Third Party or
In-House. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Support Extensive Error Reporting in Your APIs . . . . . . . . . . . . . . . . 321
Accept Multiple Formats for Output and Input . . . . . . . . . . . . . . . . . 321
Support UI Functionality in the API . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Include a Search API for Your Own Site . . . . . . . . . . . . . . . . . . . . . . . 321
Version Your API . . .
Pages:
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37