Hi,
I read about Experience APIs in one of the Apigee EBooks and just wanted to some more information about it.
1. When should one create an Experience API?
2. How is it different from a regular API?
3. What is the purpose of it?
4.What is the best practice around API consumers calling APIs to request services? In the sense
a) Is it a fair expectation of client applications/API Consumers to call APIs (GET /Products POST/Accounts) with payloads containing the API field names?
b) The alternative would be to cater to the API Consumer's database table fields and perform some transformation logic in Apigee using JS or XSLT to convert that to the API field names. Is this what an Experience API does? It just sounds inherently inefficient cause you would have overhead on your Apigee Server (On-Premise Deployment) in terms of custom logic...yet this seems to be the leading practice in System Integrations.
Sorry I'm just a little confused and would love some clarity from the Apigee Experts.
@Chris Hood @Dino
LinkedIn
Twitter
