API Design Guide
latest
  • Preface to the API Design Guide
  • Copyright
  • Principles
  • Building and using APIs
    • Use RESTful service URLs
    • Use HTTP methods and status codes
    • Use versions
    • Batching results
    • Mock behaviour
    • Support cross-domain mashups with CORS
    • Management state with HATEOAS
    • Document your API
    • Register your API
  • Secure APIs
  • Operate and improve APIs
API Design Guide
  • Docs »
  • Building and using APIs
  • Edit on GitHub

Building and using APIs¶

Recommended

Agencies are encouraged to make all digital services available as an API,

Recommended

Agencies are encouraged to deliver all APIs following ‘Pragmatic REST’ (Representational state transfer) principles detailed below.

  • Use RESTful service URLs
    • Versioning
    • Formats
    • URL Depth
    • API Payload formats
    • API Payload format encoding
    • Good RESTful URL examples
    • Bad RESTful URL examples
  • Use HTTP methods and status codes
    • Examples
    • HTTP response principles
    • Provide error responses
  • Use versions
  • Batching results
  • Mock behaviour
    • Example 1 - GET mock list of magazines
    • Example 2 - GET individual mock magazine
    • Example 3 - POST article to mock magazine
  • Support cross-domain mashups with CORS
  • Management state with HATEOAS
  • Document your API
  • Register your API

The content in this guide has been adapted from: https://github.com/WhiteHouse/api-standards

Next Previous

© Copyright 2015, AusDTO. Revision e75f82e8.

Built with Sphinx using a theme provided by Read the Docs.