> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # File many templates under one report family > Associates ONE family with many templates in a single call — the shape of the work when templates stored before families existed are filed one CADOC at a time. It is not all-or-nothing: it applies to the ids that match a live template, and answers with `matched` and `modified` so the caller learns that some of what it sent did not exist or was deleted. An id naming a soft-deleted template does not match and is not resurrected. Sending the same body twice is safe and answers `modified: 0` the second time. ## OpenAPI ````yaml /es/openapi/v3-current/reporter.yaml patch /v1/templates/category openapi: 3.1.0 info: contact: name: Discord community url: https://discord.gg/DnhqKwkGv3 description: >- This is OpenAPI documentation for Reporter. The unified reporter binary serves the REST API (RUN_MODE=api) and/or the RabbitMQ report-generation worker (RUN_MODE=worker); RUN_MODE=all runs both in one process for local development. All REST endpoints documented here serve only when RUN_MODE=api or all (port :4005); the worker (port :4006) exposes health/readyz/version only. license: name: Lerian Studio General License title: Midaz Reporter API version: 4.0.0 servers: - url: http://localhost:4005 - url: https://localhost:4005 security: - BearerAuth: [] tags: - description: Generated report instances and their lifecycle. name: Reports - description: Reusable report definitions. name: Templates - description: Interactive construction of report templates. name: Template Builder - description: Scheduled report due-date tracking. name: Deadlines - description: Configured inputs that feed report data. name: Data Sources - description: Aggregated reporting metrics. name: Metrics - description: Published business event catalog and delivery policies. name: Streaming paths: /v1/templates/category: patch: tags: - Templates summary: File many templates under one report family description: >- Associates ONE family with many templates in a single call — the shape of the work when templates stored before families existed are filed one CADOC at a time. It is not all-or-nothing: it applies to the ids that match a live template, and answers with `matched` and `modified` so the caller learns that some of what it sent did not exist or was deleted. An id naming a soft-deleted template does not match and is not resurrected. Sending the same body twice is safe and answers `modified: 0` the second time. operationId: updateTemplateCategories requestBody: content: application/json: schema: $ref: '#/components/schemas/UpdateTemplateCategoriesHumaInputBody' required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/UpdateTemplateCategoriesHumaOutputBody' description: OK '400': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Bad Request '401': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Unauthorized '403': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Forbidden '422': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Unprocessable Entity '500': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Internal Server Error components: schemas: UpdateTemplateCategoriesHumaInputBody: properties: category: description: >- Report family to file every listed template under. Case and surrounding spaces are corrected; a spelling that cannot be canonicalised is refused. examples: - cadoc type: string templateIds: description: >- Templates to file under the family. Ids that name no live template are reported through matched rather than refused. examples: - - 00000000-0000-0000-0000-000000000000 items: type: string type: - array - 'null' required: - category - templateIds type: object UpdateTemplateCategoriesHumaOutputBody: additionalProperties: false properties: category: description: The canonical family the templates were filed under examples: - cadoc type: string matched: description: How many of the ids named a live template examples: - 38 format: int64 type: integer modified: description: >- How many documents actually changed; zero when the batch was already applied examples: - 38 format: int64 type: integer required: - category - matched - modified type: object Detail: properties: code: description: >- Stable, machine-readable domain error code scoped to the emitting service (format: -NNNN). type: string detail: description: >- A human-readable explanation specific to this occurrence of the problem. examples: - Property foo is required but is missing. type: string errors: description: Optional list of individual error details examples: - - location: body.templateId message: expected string to match 'uuid' format value: not-a-uuid items: $ref: '#/components/schemas/ErrorDetail' type: - array - 'null' instance: description: >- A URI reference that identifies the specific occurrence of the problem. examples: - https://example.com/error-log/abc123 format: uri type: string status: description: HTTP status code examples: - 400 format: int64 type: integer title: description: >- A short, human-readable summary of the problem type. This value should not change between occurrences of the error. examples: - Bad Request type: string type: default: about:blank description: A URI reference to human-readable documentation for the error. examples: - https://example.com/errors/example format: uri type: string upstream: $ref: '#/components/schemas/Upstream' description: >- RFC 9457 extension member: the error a proxied third-party provider reported. Absent unless the emitting service explicitly surfaced one. type: object ErrorDetail: properties: location: description: >- Where the error occurred, e.g. 'body.items[3].tags' or 'path.thing-id' examples: - body.templateId type: string message: description: Error message text examples: - expected string to match 'uuid' format type: string value: description: The value at the given location examples: - not-a-uuid type: object Upstream: additionalProperties: false properties: code: description: The upstream provider's own error code, verbatim. examples: - E4001 type: string message: description: >- The upstream provider's own error message, verbatim (bounded, never its raw response body). examples: - account not found at provider type: string type: object securitySchemes: BearerAuth: bearerFormat: JWT description: JWT bearer token issued by the identity provider. scheme: bearer type: http ````