Good APIs Project

  • API Good Practice

    • Good Practice for Provision of APIs
      • 1.1 Plan
      • 1.2 Gather Requirements
      • 1.3 Make it Useful
      • 1.4 Keep it Simple
      • 1.5 Make it Modular
      • 1.6 Follow Standards
      • 1.7 Use Consistent Naming Structures
      • 1.8 Make it Easy to Access
      • 1.9 Let Developers Know it Exists
      • 1.10 Version Control
      • 1.11 Provide Documentation
      • 1.12 Error Handling
      • 1.13 Provide it in Different Languages
      • 1.14 Make Sure it Works
      • 1.15 Feedback
      • 1.16 Maintain your API
    • Good Practice for Consuming APIs
      • 2.1 Choose Carefully
      • 2.2 Risk Management
      • 2.3 Document
      • 2.4 Share
      • 2.5 Respect
      • 2.6 Clarity
      • 2.7 Understand Technology Limitations
      • 2.8 Keep it Simple
    • 3 Acknowledgements
    • Contact
    • What’s it All About?

Good APIs Reports in JISC Information Environment Repository

May 29th, 2009 — Marieke Guy

The Good APIs reports are now available from the JISC Information Environment Repository.

  • Report 1: JISC Good APIs Management Report
  • Report 2: API Good Practice
Posted in report. Comments Off
« Thank You from the Good APIs Project
IntroByte Briefing Documents »
Garland Wordpress Theme designed by Steven Wittens and Stefan Nagtegaal.
  •   

  • Recent Posts

    • Goodbye
    • IntroByte Briefing Documents
    • Good APIs Reports in JISC Information Environment Repository
    • Thank You from the Good APIs Project
    • Good Practice for APIs

  • Recent Comments

    • Jo Walsh on 1.8 Make it Easy to Access
    • Marieke Guy on Good Practice for Provision of APIs
    • PeteJ on 1.8 Make it Easy to Access
    • PeteJ on 1.8 Make it Easy to Access
    • PeteJ on 1.6 Follow Standards
  • May 2009
    M T W T F S S
    « Apr   Dec »
     123
    45678910
    11121314151617
    18192021222324
    25262728293031

  • RSS Delicious Bookmarks

    • What is an API? » Federated Search Blog
    • Making good software
    • How to write readable code? 5 Tips to improve your code readability. at Making good software
    • 'dev8D: JISC Developer Happiness Days', Ariadne Issue 58
    • ePublication Archive
    • Why APIs should never have been made open (and how it might’ve monetised Twitter)
    • List of APIs for your Social Networks
    • Web APIs Basics - a knol by nemetral creative
    • Mashery: Untold Secrets Behind Managing an API - ReadWriteWeb
    • Learning AJAX APIs Made Easier: Google Releases API Playground - ReadWriteWeb

  • Useful Links

    • JISC Good APIs Project

  • API books