api-client-gen

To generate a typed TypeScript API client from Strapi, you need schema.json files in your content-types directory and optional route contracts. The generator connects via the api-types-mcp toolkit and outputs client files under frontend/src/api to sync your frontend with backend definitions.

Keeping frontend TypeScript types in sync with Strapi backend changes requires generating a typed API client from content-type schemas. By running the generator after updating content types or adding new routes, you refresh the frontend API layer to faithfully match backend definitions.

Route contracts are optional for generating a TypeScript API client for Strapi. The generator requires schema.json files under backend/src/api/*/content-types/*/schema.json, while optional route contracts at backend/src/api/*/routes/*.contract.ts provide additional faithful typing for the client output.

Typed client generation from Strapi content-types works by reading schema.json files and optional route contracts to automatically produce TypeScript types. It scaffolds the frontend API layer by outputting client.ts, index.ts, types/, and namespaces/ directories directly under frontend/src/api.

You can validate API contracts before deployment by generating a typed TypeScript API client from Strapi schemas and route contracts. This ensures the frontend API layer faithfully matches the backend content-type definitions, catching contract mismatches before they reach production.

A generated Strapi TypeScript API client outputs a structured project scaffolding under frontend/src/api. This includes client.ts for the core client, index.ts for exports, a types/ directory for TypeScript definitions, and a namespaces/ directory for organized schema namespaces.