I've experienced a wide variety of approaches to how programs define their API specifications and often it leads to a number of questions such as:
- Who owns the specification?
- Who is the audience for the specification?
- How will the specification be maintained as it evolves over time?
- What format should be used to define the API Specification?
I've documented some of the best practices that the Customer Success Team at Apigee follows on engagements here but I'm keen to hear experiences from the rest of the community on the approaches being taken, what's worked well and what challenges you've faced.
LinkedIn
Twitter
