Effective API Governance: Lessons Learnt

Effective API Governance: Lessons Learnt

Talk delivered at API the Docs Amsterdam 2019

5538316cd7917cae8241cc4e6d481ad6?s=128

Alvaro Navarro

October 10, 2019
Tweet

Transcript

  1. 1.

    © 2016 Amadeus IT Group and its affiliates and subsidiaries

    Effective API Governance Lessons Learnt Alvaro Navarro Amsterdam, 10th October 2019
  2. 4.

    Once upon a time Returns the forecast purpose of a

    trip Business or Leisure based on a search criteria.
  3. 17.

    Motivation More than 20 years working with APIs ◦ EDIFACT

    ◦ SOAP/XML ◦ REST/JSON ◦ Protobuf ◦ GraphQL
  4. 34.

    Why API Governance? Design Guidelines and Standardization ❏ Errors ❏

    Endpoint/parameters naming ❏ Improvements ❏ Data Dictionaries ❏ Versioning
  5. 35.

    Why API Governance? Using URLs http://api.amadeus.com/v1/flight-search http://api.amadeus.com/2018/flight-search http://api.amadeus.com/2018/02/flight-search Using HTTP

    Header Accept: application/vnd.amadeus.v1 Accept-Version: 1 Using a Query parameter $ curl http://api.amadeus.com/flight-search?version=1
  6. 38.

    Why API Governance? import amadeus client = amadeus.Client() response =

    client.shopping.flight_destinations.get(origin = 'AMS', maxPrice = '500')
  7. 43.

    How do we make it work? Under Construction In Progress

    Pending Validated Review Process ( 1 week ) 1 to 4 weeks ❏ Validated Review Card ❏ Documentation ❏ Swagger Designer