![SIMPLICITY OF ORDER API
Integration starts with just amount field
{
"intent": "CAPTURE",
"purchase_units": [{
"amount": {
"currency_code": "USD",
"value": "100.00"
}
}]
}
purchase_unit.items:
Merchants can provide additional item information
purchase_unit.shipping_address: Merchants can
send the address they collected or get the payer
address upon buyer approval
application_context
Allows API caller to customize the buyer experience
(similar to the way Payments Experience API did
historically)
payer
When passed within the request this serves to prefill
the Hermes Guest experience. Upon buyer approval
this contains details about the Buyer.
purchase_unit.amount.breakdown: Merchants can
optionally choose to provide breakdown of amounts
(previously amount.details)
payee
For 3rd party use cases API callers can also specify the
payee.
+
+ Mix and Match objects per use caseBasic API call
© 2018 PayPal Inc. Confidential and proprietary. 8](https://image.slidesharecdn.com/tpe-api-190207014751/85/API-Product-Management-and-Strategy-8-320.jpg)
![API ECOSYSTEM
Things that make an API successful
Developer
Documentation
Accuracy
Negative
Testing,
Sandbox
API
Governance
[ML5] *
* ML – Maturity Level of API [1-5]
Debugging &
Monitoring
Notifications
SDKs
© 2018 PayPal Inc. Confidential and proprietary. 10](https://image.slidesharecdn.com/tpe-api-190207014751/85/API-Product-Management-and-Strategy-10-320.jpg)
API Product Management and Strategy
- 1. API Product Management and Strategy
- 2. Behind every successful product at PayPal there is an API 2
- 3. THE BUSINESS OF APIS Build a re-usable platform for exchanging data to power innovative applications. What is it? Why do APIs need product managers? • Rationalize requirements • API Design • Gather feedback • KPIs and measurement • Adoption Who is it targeted towards? • Merchants, partners, marketplaces, developers • Level of understanding varies 3
- 4. REQUIREMENTS • Data – customer first • Developers • Merchants • Partners • Marketplaces • Quit the internal out view – no more API jackets on organizational data • Rationalizing across multiple groups in the organization • What to build – how granular • Basic building blocks of every domain • Single integration platform – integrations that evolve as business grows © 2018 PayPal Inc. Confidential and proprietary. 4
- 5. API DESIGN • Keeping it SIMPLE • Humanizing APIs – journey from /payment, -> ebay API -> /orders • Consistency • API Governance • Style guides, standards • Constant feedback loop with external and internal integrators • Versioning and deprecation 5
- 6. API PRODUCT SOLUTIONS Merchant Engagement & Onboarding Developer Portal Partner Onboarding PayPal.com Security and Identity Identity Access Token (/v1/oauth2/token) Checkout Subscriptions InvoicingAPI Products Payment Operations Search and Reporting Backoffice APIs Payouts Authorize Capture Refund Void Transaction Reporting (/v1/reporting/transactions) Disputes List Activities (/v1/activities/activities) Strategy with least bottlenecks © 2018 PayPal Inc. Confidential and proprietary. 6
- 7. I n n o v a t i o n i n P l a t f o r m s a n d A P I s Where to start? New forms of data - addressing gaps New and simpler integration patterns on APIs Completely new features like new forms of payment (domain dependent) Architectural marvels that help with key KPIs of performance, availability, scalability etc. Completely new integration experience with ecosystem improvements
- 8. SIMPLICITY OF ORDER API Integration starts with just amount field { "intent": "CAPTURE", "purchase_units": [{ "amount": { "currency_code": "USD", "value": "100.00" } }] } purchase_unit.items: Merchants can provide additional item information purchase_unit.shipping_address: Merchants can send the address they collected or get the payer address upon buyer approval application_context Allows API caller to customize the buyer experience (similar to the way Payments Experience API did historically) payer When passed within the request this serves to prefill the Hermes Guest experience. Upon buyer approval this contains details about the Buyer. purchase_unit.amount.breakdown: Merchants can optionally choose to provide breakdown of amounts (previously amount.details) payee For 3rd party use cases API callers can also specify the payee. + + Mix and Match objects per use caseBasic API call © 2018 PayPal Inc. Confidential and proprietary. 8
- 9. API LAUNCH FRAMEWORK• API Specification / Postman Scripts • Integration Guides • Sandbox Environment • Training Programs – Internal and External • Product FAQ, Datasheet and Videos • PR and Communication • Developer Portal Updates EAT. | SLEEP. | LAUNCH. © 2018 PayPal Inc. Confidential and proprietary. 9
- 10. API ECOSYSTEM Things that make an API successful Developer Documentation Accuracy Negative Testing, Sandbox API Governance [ML5] * * ML – Maturity Level of API [1-5] Debugging & Monitoring Notifications SDKs © 2018 PayPal Inc. Confidential and proprietary. 10
- 11. SUMMARY - LESSONS LEARNT 11© 2018 PayPal Inc. Confidential and proprietary. • Treat APIs as products and understand customer needs first • Work from a minimal API structure that can grow over time • Make your default design the least constrained • API have experience too – the “integration experience” - APIs cannot be successful without the ecosystem • Versioning and deprecation – Have a clear deprecation plan for your APIs to keep the overall offering simple.