apidays LIVE Paris 2021 - APIs and the Future of Software December 7, 8 & 9, 2021 Enriching user experience thanks to API extensions Cosimo Pasquale Ricchiuto, Architect at Amadeus

1. Enriching UX
thanks to API
extensions
Cosimo Pasquale
RICCHIUTO
Dec 2021
© Amadeus ITGroup and its affiliates and subsidiaries | Confidential and restricted

2. What’s the most frustrating
about RESTAPIs?
• Multiple round trips to get data ?
• Maintaining multiple versions ?
• Clients not having controlover data returned byserver?
2
© Amadeus ITGroup and its affiliates and subsidiaries | Confidential and restricted

3. CONFIDENTIAL & RESTRICTED
restApi : {
from: “limitedControl”,
to: “RICHER_EXPERIENCE”
}
Cosimo Pasquale
RICCHIUTO
Architect
Amadeus ITGroup

4. CONFIDENTIAL & RESTRICTED
Objective
© Amadeus ITGroup and its affiliates and subsidiaries | Confidential and restricted
5
Implement
custom
business logic
Orchestrate
yourway
Integrate with
proprietaryor
3rd party
system
Unlocknewcapabilities
RESTJSONAPIs:
standardized data
exchange, but limited
interaction model
APIextensions came
up as enablerofa
richer experience

5. New York
JULY
Australia
SEPTEMBER
Singapore
APRIL
Helsinki & North
MARCH
Paris
DECEMBER
London
OCTOBER
Jakarta
FEBRUARY
Hong Kong
AUGUST
JUNE
India
MAY
Check out our API Conferences here
50+ events since 2012, 14 countries, 2,000+ speakers, 50,000+ attendees,
300k+ online community
Want to talk at one of our conferences?
Apply to speak here

6. CONFIDENTIAL & RESTRICTED
What are APIextensions?
© Amadeus ITGroup and its affiliates and subsidiaries | Confidential and restricted
6
Aframeworkfor implementingseveraltypes of
customization
YAML
OpenAPI Specification
Enrich existing
operation
1. Add new data
2. Orchestrate through
different services
New operation or
endpoint
1. Enrich the list of
available operations
2. Expose a brand-new
resource endpoint
Resource endpoint
/resource-five
GET
PATCH
DELETE
/resource-three
GET
POST PUT
/resource-four
DELETE
POST GET
/resource-two
GET
PATCH
POST
/resource-one
POST GET
Resource operations

7. CONFIDENTIAL & RESTRICTED
APIextensions guidelines
7
Keep compatibilitywith existingAPIs
 Lifecycle / deprecation policies
 Design rules
 Only incremental (no breaking) changes
 Reuse of components +patterns
 Segregate traffic via specific URIpattern
https://developers.amadeus.com/blog/api-governance
api.amadeus.com / {extensionSpace}/
{extensionIdentifier} / {version}
/ {area} / {sub-area} / {resource}
© Amadeus ITGroup and its affiliates and subsidiaries | Confidential and restricted

8. CONFIDENTIAL & RESTRICTED
APIextension definition
© Amadeus ITGroup and its affiliates and subsidiaries | Confidential and restricted 8
1. Specifydelta ofchanges
• Leveraging on AllOf
mechanism
2. Build the artifact:
• Check &validate
dependencies
• Generate dereferenced
Y
AMLfile
Endpoint
OpenAPI
specification
Operation
Operation
Brand new
operation
YAML
Brand new
endpoint
Generate artifacts based on existingcomponents
Definition

9. CONFIDENTIAL & RESTRICTED
APIGateway &server setup
© Amadeus ITGroup and its affiliates and subsidiaries | Confidential and restricted 9
https://developers.amadeus.com/blog/amadeus-for-developers-open-api-platform-architecture
Portal
API Manager
API Gateway

10. CONFIDENTIAL & RESTRICTED
APIGateway &server setup
© Amadeus ITGroup and its affiliates and subsidiaries | Confidential and restricted 10
Portal
API Manager
API Gateway
Extension API
application

11. CONFIDENTIAL & RESTRICTED
Implementation
details
11
Extension API
application
• Concrete implementation ⇒ cloud-native app
enabling:
 Abstraction layer absorbing specific traffic
 Independent technical stack
• Seamless integration
 Anyexisting UIbased on standard APIis
compatible with the extended version
• Limitations
• Manual setup limited to Enterprise APIs

12. CONFIDENTIAL & RESTRICTED
Next steps
© Amadeus ITGroup and its affiliates and subsidiaries | Confidential and restricted
12
Self-service mode to
reach more flexibility
and faster time-to-
market
Explore other
paradigms over the
Amadeus Platform for
ensuring true
openness
Move towards
serverless so to be
independent from
environment

13. Key takeaways
13
• APIextensions can help overcoming
frustration
• Integration with current APIecosystem is
keyfor a seamless experience
• Concrete implementation gave us
elements to move next

14. CONFIDENTIAL & RESTRICTED
Thanks
14