docs: add missing docs

.github/actions/spelling/expect.txt

@@ -75,7 +75,7 @@ radist
 reate
 redocly
 refetched
-Refetches
+refetches
 remarkjs
 remarkrc
 reqid
@@ -102,6 +102,7 @@ TMeta
 TMutation
 TOperation
 TPage
+TParameters
 TParams
 TQuery
 TRequest

website/docs/hooks/useInfiniteQuery.mdx

@@ -20,13 +20,15 @@ const query = api.<service>.<operation>.useInfiniteQuery(
 
 ### Arguments
 
-1.  `parameters: { path, query, header } | QueryKey | undefined`
+1.  `parameters: { path, query, header, body } | InfiniteQueryKey | undefined`
     - **Required only if OpenAPI specification defines required parameters**
     - If the operation has no required parameters according to OpenAPI, you can omit this argument
-    - `parameters` will be used to generate the `QueryKey`
-    - Instead of an object with `{path, query, header}`, you can pass a `QueryKey` as an array
+    - `parameters` will be used to generate the _Infinite Query Key_
+    - For operations generated with `--queryable-write-operations`, query parameters may also include `body`
+    - In that mode, `body` is part of the infinite query key and cache identity
+    - Mutation calls keep `body` as a separate top-level argument
+    - Instead of an object with `{ path, query, header, body }`, you can pass a typed `InfiniteQueryKey` from `getInfiniteQueryKey(...)`
       which is also strictly-typed ✨
-    - If operation does not require parameters, you must pass an empty object `{}` for strictness
 
 2.  `infiniteQueryOptions?: UseInfiniteQueryOptions`
     - **Optional**, represents the options of the [_useInfiniteQuery(...) 🌴_](https://tanstack.com/query/latest/docs/framework/react/reference/useInfiniteQuery) Hook

website/docs/hooks/useIsFetching.mdx

@@ -20,7 +20,8 @@ const queriesNumber = api.<service>.<operation>.useIsFetching(
 1.  `filters?: QueryFiltersByParameters | QueryFiltersByQueryKey`
     - **Optional**, represents the [_Query Filters 🌴_](https://tanstack.com/query/latest/docs/framework/react/guides/filters#query-filters)
       to be used. If not provided, _all_ normal and _Infinite_ queries will be used to filter.
-    - `filters.parameters: { path, query, header }` will be used for filtering queries by parameters
+    - `filters.parameters: { path, query, header, body }` filters queries by operation parameters.
+    - For operations generated with `--queryable-write-operations`, `body` can be included in `filters.parameters` and participates in query cache identity.
     - `filters.infinite: boolean` will be used to filter infinite or normal queries
     - `filters.queryKey: QueryKey` will be used for filtering queries by _QueryKey_ instead of parameters
       - `filters.queryKey` and `filters.parameters` are mutually exclusive

website/docs/hooks/useQueries.mdx

@@ -2,6 +2,9 @@
 sidebar_label: useQueries()
 ---
 
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
 # useQueries(...)
 
 The Hook enables you to concurrently execute multiple asynchronous data fetching operations.
@@ -20,7 +23,8 @@ const queries = api.<service>.<operation>.useQueries(
     - **Required**, represents the options for queries, see [_useQueries(...) 🌴_](https://tanstack.com/query/latest/docs/framework/react/reference/useQueries) documentation
     - `options.queries: QueryOptions[]`
       - **Required** array of _Queries_ to be executed
-      - `parameters: { path, query, header }` will be used for the request
+      - `parameters: { path, query, header, body }` will be used for the request
+      - For operations generated with `--queryable-write-operations`, `body` is part of the query key and cache identity
       - `queryKey: QueryKey` will be used for the request instead of the `parameters`
         - `queryKey` and `parameters` are mutually exclusive
     - `options.combine?: (result: UseQueriesResults) => TCombinedResult`
@@ -37,54 +41,77 @@ during code generation.
 
 ### Example
 
-```tsx
-import { createAPIClient } from './api'; // generated by OpenAPI Qraft
-
-import { requestFn } from '@openapi-qraft/react';
-import { QueryClient, QueryClientProvider } from '@tanstack/react-query';
-
-const queryClient = new QueryClient();
-
-const api = createAPIClient({
-  requestFn,
-  queryClient,
-  baseUrl: 'https://api.sandbox.monite.com/v1',
-});
-
-const useEntityQueries = () => {
-  /**
-   * Initiates two concurrent GET requests:
-   * ###
-   * GET /entities/3e3e-3e3e-3e3e
-   * x-monite-version: 2023-09-01
-   * ###
-   * GET /entities/5c5c-5c5c-5c5c
-   * x-monite-version: 2023-09-01
-   **/
-  return api.entities.getEntities.useQueries({
-    queries: [
-      {
-        parameters: {
-          header: {
-            'x-monite-version': '2023-09-01',
+<Tabs>
+  <TabItem value="get-queries" label="GET queries" default>
+    ```tsx
+    import { createAPIClient } from './api'; // generated by OpenAPI Qraft
+
+    import { requestFn } from '@openapi-qraft/react';
+    import { QueryClient, QueryClientProvider } from '@tanstack/react-query';
+
+    const queryClient = new QueryClient();
+
+    const api = createAPIClient({
+      requestFn,
+      queryClient,
+      baseUrl: 'https://api.sandbox.monite.com/v1',
+    });
+
+    const useEntityQueries = () => {
+      return api.entities.getEntities.useQueries({
+        queries: [
+          {
+            parameters: {
+              header: { 'x-monite-version': '2023-09-01' },
+              path: { entity_id: '3e3e-3e3e-3e3e' },
+            },
           },
-          path: {
-            entity_id: '3e3e-3e3e-3e3e',
+          {
+            parameters: {
+              header: { 'x-monite-version': '2023-09-01' },
+              path: { entity_id: '5c5c-5c5c-5c5c' },
+            },
           },
-        },
+        ],
+        combine: (results) => results.map((result) => result.data),
+      });
+    };
+    ```
+  </TabItem>
+  <TabItem value="queryable-write" label={<span>With <code>body</code></span>}>
+    ```tsx
+    const firstSearch = {
+      header: { 'x-monite-version': '1' },
+      path: { approval_policy_id: '2' },
+      body: {
+        name: 'New Name',
+        description: 'New Description',
       },
-      {
-        parameters: {
-          header: {
-            'x-monite-version': '2023-09-01',
-          },
-          path: {
-            entity_id: '5c5c-5c5c-5c5c',
-          },
-        },
+    };
+
+    const secondSearchParameters = {
+      ...firstSearch,
+      body: {
+        name: 'Another Name',
+        description: 'Another Description',
       },
-    ],
-    combine: (results) => results.map((result) => result.data),
-  });
-}
-```
+    };
+
+    const secondSearchQueryKey =
+      api.approvalPolicies.patchApprovalPoliciesId.getQueryKey(
+        secondSearchParameters
+      );
+
+    const results = api.approvalPolicies.patchApprovalPoliciesId.useQueries({
+      queries: [
+        { parameters: firstSearch },
+        { queryKey: secondSearchQueryKey },
+      ],
+    });
+
+    // Never pass `secondSearchParameters` as `queryKey` directly.
+    // `getQueryKey(...)` builds the tuple shape TanStack Query expects.
+    // `firstSearch.body` and `secondSearchParameters.body` produce different cache entries.
+    ```
+  </TabItem>
+</Tabs>

website/docs/hooks/useQuery.mdx

@@ -27,11 +27,13 @@ const query = api.<service>.<operation>.useQuery(
 
 ### Arguments
 
-1.  `parameters: { path, query, header, body? } | QueryKey | void`
+1.  `parameters: { path, query, header, body } | QueryKey | void`
     - **Required only if OpenAPI specification defines required parameters**
     - If the operation has no required parameters according to OpenAPI, you can omit this argument
     - `parameters` will be used to generate the `QueryKey`
-    - For write operations (when using `--queryable-write-operations`), you can include a `body` parameter
+    - For operations generated with `--queryable-write-operations`, query parameters may also include `body`
+    - In that mode, `body` is part of the query key and cache identity for query hooks and query-client methods
+    - Mutation calls keep `body` as a separate top-level argument
     - Instead of an object with `{ path, query, header, body }`, you can pass a `QueryKey` as an array
       which is also strictly-typed
 

website/docs/hooks/useSuspenseInfiniteQuery.mdx

@@ -18,13 +18,15 @@ const query = api.<service>.<operation>.useSuspenseInfiniteQuery(
 
 ### Arguments
 
-1.  `parameters: { path, query, header } | QueryKey | undefined`
+1.  `parameters: { path, query, header, body } | InfiniteQueryKey | undefined`
     - **Required only if OpenAPI specification defines required parameters**
     - If the operation has no required parameters according to OpenAPI, you can omit this argument
-    - `parameters` will be used to generate the `QueryKey`
-    - Instead of an object with `{path, query, header}`, you can pass a `QueryKey` as an array
+    - `parameters` will be used to generate the _Infinite Query Key_
+    - For operations generated with `--queryable-write-operations`, query parameters may also include `body`
+    - In that mode, `body` is part of the infinite query key and cache identity
+    - Mutation calls keep `body` as a separate top-level argument
+    - Instead of an object with `{ path, query, header, body }`, you can pass a typed `InfiniteQueryKey` from `getInfiniteQueryKey(...)`
       which is also strictly-typed ✨
-    - If operation does not require parameters, you must pass an empty object `{}` for strictness
 
 2.  `suspenseInfiniteQueryOptions?: UseSuspenseInfiniteQueryOptions`
     - **Optional**, represents the options of the

website/docs/hooks/useSuspenseQueries.mdx

@@ -23,7 +23,8 @@ const result = api.<service>.<operation>.useSuspenseQueries(
     - **Required**, represents the options for queries, see [_useSuspenseQueries(...) 🌴_](https://tanstack.com/query/latest/docs/framework/react/reference/useSuspenseQueries) documentation
     - `options.queries: QueryOptions[]`
       - **Required** array of _Queries_ to be executed
-      - `parameters: { path, query, header }` will be used for the request
+      - `parameters: { path, query, header, body }` will be used for the request
+      - For operations generated with `--queryable-write-operations`, `body` is part of the query key and cache identity
       - `queryKey: QueryKey` will be used for the request instead of the `parameters`
         - `queryKey` and `parameters` are mutually exclusive
     - `options.combine?: (result: UseQueriesResults) => TCombinedResult`
@@ -109,3 +110,30 @@ export default function() {
   )
 }
 ```
+
+### Queryable Write Operations
+
+For operations generated with `--queryable-write-operations`, `useSuspenseQueries` accepts the same `parameters.body`
+shape as `useQueries`. Each distinct body is part of the query key and creates a distinct cache entry.
+
+```tsx
+const queryKey =
+  api.approvalPolicies.patchApprovalPoliciesId.getQueryKey({
+    header: { 'x-monite-version': '1' },
+    path: { approval_policy_id: '2' },
+    body: { name: 'Another Name' },
+  });
+
+const results = api.approvalPolicies.patchApprovalPoliciesId.useSuspenseQueries({
+  queries: [
+    {
+      parameters: {
+        header: { 'x-monite-version': '1' },
+        path: { approval_policy_id: '2' },
+        body: { name: 'New Name' },
+      },
+    },
+    { queryKey },
+  ],
+});
+```

website/docs/hooks/useSuspenseQuery.mdx

@@ -20,13 +20,15 @@ const result = api.<service>.<operation>.useSuspenseQuery(
 
 ### Arguments
 
-1.  `parameters: { path, query, header } | QueryKey | void`
+1.  `parameters: { path, query, header, body } | QueryKey | void`
     - **Required only if OpenAPI specification defines required parameters**
     - If the operation has no required parameters according to OpenAPI, you can omit this argument
     - `parameters` will be used to generate the `QueryKey`
-    - Instead of an object with `{path, query, header}`, you can pass a `QueryKey` as an array
+    - For operations generated with `--queryable-write-operations`, query parameters may also include `body`
+    - In that mode, `body` is part of the query key and cache identity for query hooks and query-client methods
+    - Mutation calls keep `body` as a separate top-level argument
+    - Instead of an object with `{ path, query, header, body }`, you can pass a `QueryKey` as an array
       which is also strictly-typed ✨
-    - If operation does not require parameters, you must pass an empty object `{}` for strictness
 
 2.  `queryOptions?: UseQueryOptions`
     - **Optional**, represents the options of the [_useSuspenseQuery(...) 🌴_](https://tanstack.com/query/latest/docs/framework/react/reference/useSuspenseQuery) Hook

website/docs/query-client/cancelQueries.mdx

@@ -25,7 +25,8 @@ guide for more information.
     1.  `filters: QueryFiltersByParameters | QueryFiltersByQueryKey`
         - **Required**, represents the [_Query Filters 🌴_](https://tanstack.com/query/latest/docs/framework/react/guides/filters#query-filters)
           to be used, strictly-typed ✨
-        - `filters.parameters: { path, query, header }` will be used for filtering queries by parameters
+        - `filters.parameters: { path, query, header, body }` filters queries by operation parameters.
+        - For operations generated with `--queryable-write-operations`, `body` can be included in `filters.parameters` and participates in query cache identity.
         - `filters.infinite?: boolean` will be used to filter infinite or normal queries, **Required** if `predicate` is provided
         - `filters.queryKey?: QueryKey` will be used for filtering queries by _QueryKey_ instead of ~~`parameters`~~
           - `filters.queryKey` and `filters.parameters` are mutually exclusive
@@ -45,7 +46,8 @@ guide for more information.
     1.  `filters: QueryFiltersByParameters | QueryFiltersByQueryKey`
         - **Required**, represents the [_Query Filters 🌴_](https://tanstack.com/query/latest/docs/framework/react/guides/filters#query-filters)
           to be used, strictly-typed ✨
-        - `filters.parameters: { path, query, header }` will be used for filtering queries by parameters
+        - `filters.parameters: { path, query, header, body }` filters queries by operation parameters.
+        - For operations generated with `--queryable-write-operations`, `body` can be included in `filters.parameters` and participates in query cache identity.
         - `filters.infinite?: boolean` will be used to filter infinite or normal queries, **Required** if `predicate` is provided
         - `filters.queryKey?: QueryKey` will be used for filtering queries by _QueryKey_ instead of ~~`parameters`~~
           - `filters.queryKey` and `filters.parameters` are mutually exclusive

website/docs/query-client/ensureInfiniteQueryData.mdx

@@ -22,9 +22,12 @@ const result = api.<service>.<operation>.ensureInfiniteQueryData({
 ```
 
 ### Arguments
-1.  - `parameters: { path, query, header } | QueryKey | void`
+1.  -  `parameters: { path, query, header, body } | InfiniteQueryKey | void`
       - OpenAPI request parameters for the query, strictly-typed ✨
-      - `parameters` will be used to generate the `QueryKey`
+      - `parameters` will be used to generate the _Infinite Query Key_
+      - For operations generated with `--queryable-write-operations`, query parameters may also include `body`
+      - In that mode, `body` is part of the infinite query key and cache identity
+      - Mutation calls keep `body` as a separate top-level argument
     - `fetchInfiniteQueryOptions?: FetchInfiniteQueryOptions`
       - `requestFn?: RequestFn`
         - **Optional**, a function that will be used to execute the request

website/docs/query-client/ensureQueryData.mdx

@@ -22,9 +22,12 @@ const result = api.<service>.<operation>.ensureQueryData({
 
 ### Arguments
 
-1. -  `parameters: { path, query, header } | QueryKey | void`
+1. -  `parameters: { path, query, header, body } | QueryKey | void`
       - **Required**, OpenAPI request parameters for the query, strictly-typed ✨
       - `parameters` will be used to generate the `QueryKey`
+      - For operations generated with `--queryable-write-operations`, query parameters may also include `body`
+      - In that mode, `body` is part of the query key and cache identity for query-client methods
+      - Mutation calls keep `body` as a separate top-level argument
       - `requestFn?: RequestFn`
         - **Optional**, a function that will be used to execute the request
       - `revalidateIfStale?: boolean`

website/docs/query-client/fetchInfiniteQuery.mdx

@@ -26,9 +26,12 @@ const result = api.<service>.<operation>.fetchInfiniteQuery(
 
 ### Arguments
 
-1.  -  `parameters: { path, query, header } | QueryKey | void`
+1.  -  `parameters: { path, query, header, body } | InfiniteQueryKey | void`
       - OpenAPI request parameters for the query, strictly-typed ✨
-      - `parameters` will be used to generate the `QueryKey`
+      - `parameters` will be used to generate the _Infinite Query Key_
+      - For operations generated with `--queryable-write-operations`, query parameters may also include `body`
+      - In that mode, `body` is part of the infinite query key and cache identity
+      - Mutation calls keep `body` as a separate top-level argument
     -  `fetchInfiniteQueryOptions?: FetchInfiniteQueryOptions`
       - `requestFn?: RequestFn`
         - **Optional**, a function that will be used to execute the request

website/docs/query-client/fetchQuery.mdx

@@ -29,9 +29,12 @@ const result = api.<service>.<operation>.fetchQuery(
 
 ### Arguments
 
-1. -  `parameters: { path, query, header } | QueryKey | void`
+1. -  `parameters: { path, query, header, body } | QueryKey | void`
       - **Required**, OpenAPI request parameters for the query, strictly-typed ✨
       - `parameters` will be used to generate the `QueryKey`
+      - For operations generated with `--queryable-write-operations`, query parameters may also include `body`
+      - In that mode, `body` is part of the query key and cache identity for query-client methods
+      - Mutation calls keep `body` as a separate top-level argument
       - `requestFn?: RequestFn`
         - **Optional**, a function that will be used to execute the request
       - `baseUrl?: string`
@@ -70,6 +73,20 @@ const result = api.<service>.<operation>.fetchQuery(
     );
     ```
   </TabItem>
+  <TabItem value="queryable-write" label={<span>With <code>body</code></span>}>
+    ```ts
+    const policy = await api.approvalPolicies.patchApprovalPoliciesId.fetchQuery({
+      parameters: {
+        header: { 'x-monite-version': '1' },
+        path: { approval_policy_id: '2' },
+        body: {
+          name: 'New Name',
+          description: 'New Description',
+        },
+      },
+    });
+    ```
+  </TabItem>
   <TabItem value="with-query-fn" label={<span style={{verticalAlign: 'middle'}}>With <code>queryFn</code></span>}>
     ```ts
     import { createAPIClient } from './api'; // generated by OpenAPI Qraft CLI