Documentation and OpenAPI specification for the DoDays API - providing access to family account management at dodays.co.uk.
This repository contains:
- OpenAPI 3.1 Specification (
openapi.yaml) - Complete API specification for the DoDays API - API Documentation - Human-readable markdown documentation
- Code Generation Configuration - Settings for generating SDKs and documentation from the OpenAPI spec
The OpenAPI specification in this repository is the source of truth for the DoDays API and is used to automatically generate the TypeScript SDK.
- Node.js (v24.9.0 or higher)
- pnpm
# Using pnpm
pnpm install# Generate code from the OpenAPI spec
npx @openapitools/openapi-generator-cli generate
# List available generators
npx @openapitools/openapi-generator-cli listThe openapi.yaml specification automatically generates the TypeScript SDK (@dodayslabs/ts-sdk) located on npm at package/@dodayslabs/ts-sdk:
- Generator:
typescript-fetch(OpenAPI Generator CLI) - Output: ts-sdk/src
- Build Commands (run from ts-sdk directory):
pnpm generate # Generate TypeScript client pnpm compile # Compile TypeScript to JavaScript pnpm build # Run both generate and compile
⚠️ Important: Changes toopenapi.yamldirectly affect the generated TypeScript SDK. After modifying the specification:
- Ensure compatibility with the
typescript-fetchgenerator- Regenerate the SDK
- Test the SDK thoroughly
- Version breaking changes appropriately
.
├── openapi.yaml # OpenAPI 3.1 specification
├── openapitools.json # OpenAPI Generator CLI configuration
├── 01-Introduction.md # API introduction and overview
├── 02-Authentication.md # Authentication flow documentation
└── README.md # This file
- Authentication: Token-based (72-hour expiry)
- Environments: Local, Staging, Production
- Contact: engineering@dodays.co.uk
- Introduction - Getting started with the DoDays API
- Authentication - Authentication flow and token management
When modifying the OpenAPI specification:
- Ensure all endpoint definitions, schemas, and examples are valid
- Maintain compatibility with code generators
- Update relevant documentation files
- Test generated code after changes
- Follow semantic versioning for breaking changes