This document discusses various lessons learned from building APIs and integrating with third party services. It covers topics like caching data to reduce external requests, handling endpoint and data format changes from third parties, and flexibility to extend beyond existing APIs. The document also provides examples of setting up email services and links to video files on Facebook.
20. 3RD PARTY
BUG FIXES
Minimise the number of places you write your work-arounds to issues, and
places you cleanse any invalid data returned. Document it once.
22. Create ad using 鍖le_get_contents() as per Facebook documentation
23. Create ad using exec CURL as per Facebook documentation in same post
24. ENDPOINT
CHANGES
Changes by third parties to the available endpoints, whether the data format
returned, or the actual endpoint to request
29. REQUEST TO MY API
IS IT AN OBJECT OR FEED?
OBJECT FEED
DO I WANT A SPECIFIC CONNECTIONS NO
DID I REQUEST IT FROM FB
IN THE LAST X MINUTES?
CONNECTIONS?
STATIC YES
REQUEST OBJECT FROM MAKE REQUEST TO
OWN DATABASE FACEBOOK
CLEANSE AND STORE RESPONSE IN
SEND RESPONSE DATABASE
30. CHANGE
SERVICES
Change services, this could be email providers handling your transactional
email for noti鍖cations. Changing updates to Twitter rather than FB, or maps
data to format for OpenMaps rather than Google. Or anything else.