Here at FixSpec we think of API documentation as a “contract” between two parties. It describes available messages, fields, and enumerations and workflows. It tells readers that if they send X in, they can expect Y in return.
Customer-specific specs take this a step further by removing anything that a specific customer doesn’t use, and extends the documentation to capture bespoke customisations and transformations. This has a number of benefits to both the sender and receiver.
In this episode of #doFIXdifferently, Chris Lees explores what customer-specific specs are, how you can go about creating them, and why this is worth your time.