API Documentation
Reference and conceptual API docs built on a contract-first OpenAPI workflow, organized around key developer questions.

I create API documentation across both reference and conceptual layers to help developers integrate APIs efficiently.
For reference documentation, I work within a contract-first workflow using OpenAPI specifications. I review and refine API contracts in YAML or JSON, improving endpoint summaries, parameter and schema descriptions, response models, and request/response examples to ensure clarity and usability in tools such as Swagger UI.
Because API contracts drive autogenerated documentation, SDKs, and developer portals, I focus on consistency, clear terminology, and accurate schema descriptions early in the design process. I also identify naming inconsistencies, unclear error messaging, and documentation gaps before implementation progresses.
For conceptual documentation, I create supporting content such as onboarding guides, authentication requirements, pagination and rate limiting guidance, error handling information, and integration best practices. These materials provide the context developers need beyond endpoint references alone.
Across both layers, I organise content around key developer questions: what the API does, when to use it, and what is required to implement it successfully. The result is documentation that improves usability, reduces onboarding time, and helps prevent integration errors.
Download: API Documentation Sample (PDF) · Live API reference on SAP Business Accelerator Hub