@insurance-broker/api-client 5.50.0 → 5.51.0

package/dist/schema.d.ts

@@ -3080,7 +3080,7 @@ export interface paths {
         patch?: never;
         trace?: never;
     };
-    "/api/v1/customer-account": {
+    "/api/v1/customers/{id}/timeline": {
         parameters: {
             query?: never;
             header?: never;
@@ -3088,12 +3088,14 @@ export interface paths {
             cookie?: never;
         };
         /**
-         * The account this broker holds for the signed-in customer.
-         * @description **A `403` here is usually not an error.** `urn:brokerplatform:problem:customer-not-attached` means this sign-in has never been linked to a broker — the ordinary state of a customer who has registered but not yet redeemed an invitation, and the cue to show onboarding rather than a failure. A `403` *without* that type is an ordinary refusal and must not be read as onboarding: it is what a caller whose broker may not transact receives, and what a caller whose account the broker has suspended or closed receives.
+         * Read what has happened on a customer's relationship with the broker
+         * @description CRM-008. Policies, claims, payments, quotes and form submissions as their modules report them, with the notes, logged calls and emails, shares and next actions staff recorded here. Newest first. Each row says what kind of thing happened and when. It never carries a note's words: read those through the notes route, which needs `crm.customer-notes.read`.
          *
-         *     **The `404` is retained for compatibility and is not the unattached state.** It means the caller holds the permission and the record is gone, which cannot happen through this API today; a client keying its onboarding branch on `404` will never reach it.
+         *     The timeline begins when this release was deployed; earlier activity is not on it.
+         *
+         *     Paged by cursor (ADR-0031): pass `nextCursor` back as `cursor` until it is null. A cursor this list did not issue is a `400`.
          */
-        get: operations["GetOwnCustomerAccount"];
+        get: operations["ListCustomerTimeline"];
         put?: never;
         post?: never;
         delete?: never;
@@ -3102,7 +3104,35 @@ export interface paths {
         patch?: never;
         trace?: never;
     };
-    "/api/v1/customer-account/sessions/revocation": {
+    "/api/v1/customer-verification-methods": {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        /**
+         * The ways this broker's staff may verify a customer before signing them out, in the broker's order.
+         * @description The broker's closed set of verification methods (ADR-0049). A member of staff signing a customer out of every session picks one of these keys and the choice is recorded in the audit entry. The set is configuration, never without an active method once configured; an empty list means this broker has not configured one yet, and staff-assisted sign-out is refused until it does.
+         *
+         *     **Only active methods by default**, because only those can be chosen. `includeRetired=true` adds the retired ones, marked `isActive: false` with `retiredAtUtc`, for somebody managing the set (#648); they cannot be chosen and keep their keys.
+         */
+        get: operations["ListCustomerVerificationMethods"];
+        put?: never;
+        /**
+         * Add a way this broker's staff may verify a customer before signing them out
+         * @description #648. `key` is a stable identifier — lower-case letters, digits and hyphens, at most 64 characters — unique within this broker and never changed or reused, because audit entries for staff sign-outs record it. `name` is what staff read, at most 120 characters; `description`, optional and at most 500, says what staff must actually have checked. Neither may hold control or invisible formatting characters. The method is appended to the end of the set and is active at once. A broker with no set may add its first method here.
+         *
+         *     **Refusals.** `400` for a malformed field. `409` `urn:brokerplatform:problem:verification-method-key-taken` when this broker already has a method with that key, active or retired: choose another key, or reactivate the retired one.
+         */
+        post: operations["AddCustomerVerificationMethod"];
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
+    "/api/v1/customers/{id}/sessions/revocation": {
         parameters: {
             query?: never;
             header?: never;
@@ -3112,40 +3142,40 @@ export interface paths {
         get?: never;
         put?: never;
         /**
-         * Signs the customer out of every session they have established, including this one.
-         * @description **Every sign-in this customer established up to now stops working against this API on its next request — including the one making this call.** That is the stolen-device remedy (SEC-012): a phone that is lost keeps a session the customer cannot reach, and this ends what that session can do here without needing the phone.
+         * Signs a customer out of every session they have established, after a member of staff has verified them.
+         * @description **Every sign-in this customer established up to now stops working against this API on its next request** — the same effect as the customer's own `POST /api/v1/customer-account/sessions/revocation`, for a customer who rings in because a device was lost or stolen (SEC-012). The customer signs in again afterwards on the device they hold.
          *
-         *     **What a client must do afterwards.** Every request from a session established before the returned `revokedAtUtc` (plus a few seconds' clock allowance) is answered `401` with problem type `urn:brokerplatform:problem:session-revoked` — on any customer route, not only this one. **Do not refresh in answer to it**: the identity provider will issue a new token and that token will be refused the same way, because it belongs to the same sign-in. **Do not answer it with a `prompt=login` sign-in alone either**: on a device that still holds the identity provider's session cookie, that re-authenticates the *same* session and re-admits every refresh token copied from it. End the identity provider's session first (RP-initiated logout with `id_token_hint`), discard the stored tokens, then sign in.
+         *     **Verify the customer first, then say how.** `verificationMethod` is a key from `GET /api/v1/customer-verification-methods`, this broker's closed set; `reason` is required, at most 500 characters, and is recorded with the method and the member of staff in the audit entry on the customer record (action `crm.customer.sessions-revoked-by-staff`). Tell the customer to change their password and secure their email account: signing out does not stop somebody who knows the password.
          *
-         *     **Tell the customer to change their password, and to secure their email account.** Signing out does not stop somebody who knows the password from signing in again, and a password can be reset through the email address.
+         *     **Refusals.** `400` when either field is missing or the reason is too long. `404` when the customer is not this broker's. `409` with problem type `urn:brokerplatform:problem:verification-method-not-offered` when the method is not in this broker's set, has been retired, or the broker has configured none — read the set and choose from it. `409` with no type when the customer has never attached a sign-in account, so has no session to end.
          *
-         *     **Where a deployment has enabled the isolated identity-management component (ADR-0049), the identity provider's sessions are also ended**, shortly after this answer and not before it: the request is recorded here and carried out in the background. Nowhere is that a reason to skip the steps above. It does not list sessions, or end one and keep the others. A `409` means the caller is acting for an organisation: sessions belong to the person, so act personally to revoke them.
+         *     **Where a deployment has enabled the isolated identity-management component (ADR-0049), the identity provider's sessions are also ended**, shortly after this answer and not before it, on this member of staff's own sign-in: the request is recorded here and carried out in the background. It does not list sessions.
          */
-        post: operations["RevokeOwnCustomerSessions"];
+        post: operations["RevokeCustomerSessions"];
         delete?: never;
         options?: never;
         head?: never;
         patch?: never;
         trace?: never;
     };
-    "/api/v1/customer-account/redemption": {
+    "/api/v1/customer/contexts": {
         parameters: {
             query?: never;
             header?: never;
             path?: never;
             cookie?: never;
         };
-        get?: never;
+        /** The parties the signed-in customer may act as: themselves, and every organisation they hold an active membership of. The identifier of each is what X-Broker-Acting-For takes. */
+        get: operations["ListActingContexts"];
         put?: never;
-        /** Attaches the signed-in account to the customer an invitation was issued for. The code travels in the X-Broker-Invitation header. */
-        post: operations["RedeemCustomerInvitation"];
+        post?: never;
         delete?: never;
         options?: never;
         head?: never;
         patch?: never;
         trace?: never;
     };
-    "/api/v1/customer-verification-methods": {
+    "/api/v1/customer-account": {
         parameters: {
             query?: never;
             header?: never;
@@ -3153,27 +3183,21 @@ export interface paths {
             cookie?: never;
         };
         /**
-         * The ways this broker's staff may verify a customer before signing them out, in the broker's order.
-         * @description The broker's closed set of verification methods (ADR-0049). A member of staff signing a customer out of every session picks one of these keys and the choice is recorded in the audit entry. The set is configuration, never without an active method once configured; an empty list means this broker has not configured one yet, and staff-assisted sign-out is refused until it does.
+         * The account this broker holds for the signed-in customer.
+         * @description **A `403` here is usually not an error.** `urn:brokerplatform:problem:customer-not-attached` means this sign-in has never been linked to a broker — the ordinary state of a customer who has registered but not yet redeemed an invitation, and the cue to show onboarding rather than a failure. A `403` *without* that type is an ordinary refusal and must not be read as onboarding: it is what a caller whose broker may not transact receives, and what a caller whose account the broker has suspended or closed receives.
          *
-         *     **Only active methods by default**, because only those can be chosen. `includeRetired=true` adds the retired ones, marked `isActive: false` with `retiredAtUtc`, for somebody managing the set (#648); they cannot be chosen and keep their keys.
+         *     **The `404` is retained for compatibility and is not the unattached state.** It means the caller holds the permission and the record is gone, which cannot happen through this API today; a client keying its onboarding branch on `404` will never reach it.
          */
-        get: operations["ListCustomerVerificationMethods"];
+        get: operations["GetOwnCustomerAccount"];
         put?: never;
-        /**
-         * Add a way this broker's staff may verify a customer before signing them out
-         * @description #648. `key` is a stable identifier — lower-case letters, digits and hyphens, at most 64 characters — unique within this broker and never changed or reused, because audit entries for staff sign-outs record it. `name` is what staff read, at most 120 characters; `description`, optional and at most 500, says what staff must actually have checked. Neither may hold control or invisible formatting characters. The method is appended to the end of the set and is active at once. A broker with no set may add its first method here.
-         *
-         *     **Refusals.** `400` for a malformed field. `409` `urn:brokerplatform:problem:verification-method-key-taken` when this broker already has a method with that key, active or retired: choose another key, or reactivate the retired one.
-         */
-        post: operations["AddCustomerVerificationMethod"];
+        post?: never;
         delete?: never;
         options?: never;
         head?: never;
         patch?: never;
         trace?: never;
     };
-    "/api/v1/customers/{id}/sessions/revocation": {
+    "/api/v1/customer-account/sessions/revocation": {
         parameters: {
             query?: never;
             header?: never;
@@ -3183,33 +3207,33 @@ export interface paths {
         get?: never;
         put?: never;
         /**
-         * Signs a customer out of every session they have established, after a member of staff has verified them.
-         * @description **Every sign-in this customer established up to now stops working against this API on its next request** — the same effect as the customer's own `POST /api/v1/customer-account/sessions/revocation`, for a customer who rings in because a device was lost or stolen (SEC-012). The customer signs in again afterwards on the device they hold.
+         * Signs the customer out of every session they have established, including this one.
+         * @description **Every sign-in this customer established up to now stops working against this API on its next request — including the one making this call.** That is the stolen-device remedy (SEC-012): a phone that is lost keeps a session the customer cannot reach, and this ends what that session can do here without needing the phone.
          *
-         *     **Verify the customer first, then say how.** `verificationMethod` is a key from `GET /api/v1/customer-verification-methods`, this broker's closed set; `reason` is required, at most 500 characters, and is recorded with the method and the member of staff in the audit entry on the customer record (action `crm.customer.sessions-revoked-by-staff`). Tell the customer to change their password and secure their email account: signing out does not stop somebody who knows the password.
+         *     **What a client must do afterwards.** Every request from a session established before the returned `revokedAtUtc` (plus a few seconds' clock allowance) is answered `401` with problem type `urn:brokerplatform:problem:session-revoked` — on any customer route, not only this one. **Do not refresh in answer to it**: the identity provider will issue a new token and that token will be refused the same way, because it belongs to the same sign-in. **Do not answer it with a `prompt=login` sign-in alone either**: on a device that still holds the identity provider's session cookie, that re-authenticates the *same* session and re-admits every refresh token copied from it. End the identity provider's session first (RP-initiated logout with `id_token_hint`), discard the stored tokens, then sign in.
          *
-         *     **Refusals.** `400` when either field is missing or the reason is too long. `404` when the customer is not this broker's. `409` with problem type `urn:brokerplatform:problem:verification-method-not-offered` when the method is not in this broker's set, has been retired, or the broker has configured none — read the set and choose from it. `409` with no type when the customer has never attached a sign-in account, so has no session to end.
+         *     **Tell the customer to change their password, and to secure their email account.** Signing out does not stop somebody who knows the password from signing in again, and a password can be reset through the email address.
          *
-         *     **Where a deployment has enabled the isolated identity-management component (ADR-0049), the identity provider's sessions are also ended**, shortly after this answer and not before it, on this member of staff's own sign-in: the request is recorded here and carried out in the background. It does not list sessions.
+         *     **Where a deployment has enabled the isolated identity-management component (ADR-0049), the identity provider's sessions are also ended**, shortly after this answer and not before it: the request is recorded here and carried out in the background. Nowhere is that a reason to skip the steps above. It does not list sessions, or end one and keep the others. A `409` means the caller is acting for an organisation: sessions belong to the person, so act personally to revoke them.
          */
-        post: operations["RevokeCustomerSessions"];
+        post: operations["RevokeOwnCustomerSessions"];
         delete?: never;
         options?: never;
         head?: never;
         patch?: never;
         trace?: never;
     };
-    "/api/v1/customer/contexts": {
+    "/api/v1/customer-account/redemption": {
         parameters: {
             query?: never;
             header?: never;
             path?: never;
             cookie?: never;
         };
-        /** The parties the signed-in customer may act as: themselves, and every organisation they hold an active membership of. The identifier of each is what X-Broker-Acting-For takes. */
-        get: operations["ListActingContexts"];
+        get?: never;
         put?: never;
-        post?: never;
+        /** Attaches the signed-in account to the customer an invitation was issued for. The code travels in the X-Broker-Invitation header. */
+        post: operations["RedeemCustomerInvitation"];
         delete?: never;
         options?: never;
         head?: never;
@@ -8059,6 +8083,20 @@ export interface components {
             help: null | string;
             section: null | string;
         };
+        CustomerTimelineEntryResponse: {
+            /** Format: uuid */
+            id: string;
+            kind: string;
+            source: string;
+            /** Format: uuid */
+            referenceId: null | string;
+            /** Format: date-time */
+            occurredAtUtc: string;
+        };
+        CustomerTimelinePage: {
+            items: components["schemas"]["CustomerTimelineEntryResponse"][];
+            nextCursor: null | string;
+        };
         CustomerVerificationMethodResponse: {
             key: string;
             name: string;
@@ -17957,14 +17995,16 @@ export interface operations {
             };
         };
     };
-    GetOwnCustomerAccount: {
+    ListCustomerTimeline: {
         parameters: {
-            query?: never;
-            header?: {
-                /** @description The organisation to act for: one of the identifiers GET /api/v1/customer/contexts lists. Omit it, or send it empty, to act for your own account; there is no mode in which it becomes mandatory. A value you hold no active membership of, or one that is not an organisation identifier, is refused with 403 naming nothing, and never quietly treated as your own account. */
-                "X-Broker-Acting-For"?: components["parameters"]["ActingFor"];
+            query?: {
+                cursor?: string;
+                limit?: number | string;
+            };
+            header?: never;
+            path: {
+                id: string;
             };
-            path?: never;
             cookie?: never;
         };
         requestBody?: never;
@@ -17972,101 +18012,30 @@ export interface operations {
             /** @description OK */
             200: {
                 headers: {
-                    /** @description The party this request actually acted for. Present, carrying the organisation identifier, when it acted for an organisation; absent when it acted for your own account. It mirrors the request header, so it can be sent back unchanged. Compare it with what you meant to send: it is the only way to see that a request you meant for an organisation was made personally. */
-                    "X-Broker-Acting-For"?: string;
                     [name: string]: unknown;
                 };
                 content: {
-                    "application/json": components["schemas"]["OwnCustomerAccountResponse"];
+                    "application/json": components["schemas"]["CustomerTimelinePage"];
                 };
             };
-            /** @description Forbidden */
-            403: {
+            /** @description Bad Request */
+            400: {
                 headers: {
-                    /** @description The party this request actually acted for. Present, carrying the organisation identifier, when it acted for an organisation; absent when it acted for your own account. It mirrors the request header, so it can be sent back unchanged. Compare it with what you meant to send: it is the only way to see that a request you meant for an organisation was made personally. */
-                    "X-Broker-Acting-For"?: string;
                     [name: string]: unknown;
                 };
                 content: {
-                    "application/problem+json": components["schemas"]["ProblemDetails"];
+                    "application/problem+json": components["schemas"]["HttpValidationProblemDetails"];
                 };
             };
             /** @description Not Found */
             404: {
                 headers: {
-                    /** @description The party this request actually acted for. Present, carrying the organisation identifier, when it acted for an organisation; absent when it acted for your own account. It mirrors the request header, so it can be sent back unchanged. Compare it with what you meant to send: it is the only way to see that a request you meant for an organisation was made personally. */
-                    "X-Broker-Acting-For"?: string;
                     [name: string]: unknown;
                 };
                 content?: never;
             };
         };
     };
-    RevokeOwnCustomerSessions: {
-        parameters: {
-            query?: never;
-            header?: {
-                /** @description The organisation to act for: one of the identifiers GET /api/v1/customer/contexts lists. Omit it, or send it empty, to act for your own account; there is no mode in which it becomes mandatory. A value you hold no active membership of, or one that is not an organisation identifier, is refused with 403 naming nothing, and never quietly treated as your own account. */
-                "X-Broker-Acting-For"?: components["parameters"]["ActingFor"];
-            };
-            path?: never;
-            cookie?: never;
-        };
-        requestBody?: never;
-        responses: {
-            /** @description OK */
-            200: {
-                headers: {
-                    /** @description The party this request actually acted for. Present, carrying the organisation identifier, when it acted for an organisation; absent when it acted for your own account. It mirrors the request header, so it can be sent back unchanged. Compare it with what you meant to send: it is the only way to see that a request you meant for an organisation was made personally. */
-                    "X-Broker-Acting-For"?: string;
-                    [name: string]: unknown;
-                };
-                content: {
-                    "application/json": components["schemas"]["CustomerSessionRevocationResponse"];
-                };
-            };
-            /** @description Conflict. A type of urn:brokerplatform:problem:concurrency-conflict means someone else changed the record first and nothing was written: read it again and decide again. Any other type is a conflict this operation decided itself, and retrying it unchanged will not help. */
-            409: {
-                headers: {
-                    /** @description The party this request actually acted for. Present, carrying the organisation identifier, when it acted for an organisation; absent when it acted for your own account. It mirrors the request header, so it can be sent back unchanged. Compare it with what you meant to send: it is the only way to see that a request you meant for an organisation was made personally. */
-                    "X-Broker-Acting-For"?: string;
-                    [name: string]: unknown;
-                };
-                content: {
-                    "application/problem+json": components["schemas"]["ConcurrencyConflictProblem"] | components["schemas"]["ProblemDetails"];
-                };
-            };
-        };
-    };
-    RedeemCustomerInvitation: {
-        parameters: {
-            query?: never;
-            header?: never;
-            path?: never;
-            cookie?: never;
-        };
-        requestBody?: never;
-        responses: {
-            /** @description OK */
-            200: {
-                headers: {
-                    [name: string]: unknown;
-                };
-                content: {
-                    "application/json": components["schemas"]["RedeemedCustomerAccountResponse"];
-                };
-            };
-            /** @description Conflict. A type of urn:brokerplatform:problem:concurrency-conflict means someone else changed the record first and nothing was written: read it again and decide again. Any other type is a conflict this operation decided itself, and retrying it unchanged will not help. */
-            409: {
-                headers: {
-                    [name: string]: unknown;
-                };
-                content: {
-                    "application/problem+json": components["schemas"]["ConcurrencyConflictProblem"] | components["schemas"]["ProblemDetails"];
-                };
-            };
-        };
-    };
     ListCustomerVerificationMethods: {
         parameters: {
             query?: {
@@ -18207,6 +18176,116 @@ export interface operations {
             };
         };
     };
+    GetOwnCustomerAccount: {
+        parameters: {
+            query?: never;
+            header?: {
+                /** @description The organisation to act for: one of the identifiers GET /api/v1/customer/contexts lists. Omit it, or send it empty, to act for your own account; there is no mode in which it becomes mandatory. A value you hold no active membership of, or one that is not an organisation identifier, is refused with 403 naming nothing, and never quietly treated as your own account. */
+                "X-Broker-Acting-For"?: components["parameters"]["ActingFor"];
+            };
+            path?: never;
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description OK */
+            200: {
+                headers: {
+                    /** @description The party this request actually acted for. Present, carrying the organisation identifier, when it acted for an organisation; absent when it acted for your own account. It mirrors the request header, so it can be sent back unchanged. Compare it with what you meant to send: it is the only way to see that a request you meant for an organisation was made personally. */
+                    "X-Broker-Acting-For"?: string;
+                    [name: string]: unknown;
+                };
+                content: {
+                    "application/json": components["schemas"]["OwnCustomerAccountResponse"];
+                };
+            };
+            /** @description Forbidden */
+            403: {
+                headers: {
+                    /** @description The party this request actually acted for. Present, carrying the organisation identifier, when it acted for an organisation; absent when it acted for your own account. It mirrors the request header, so it can be sent back unchanged. Compare it with what you meant to send: it is the only way to see that a request you meant for an organisation was made personally. */
+                    "X-Broker-Acting-For"?: string;
+                    [name: string]: unknown;
+                };
+                content: {
+                    "application/problem+json": components["schemas"]["ProblemDetails"];
+                };
+            };
+            /** @description Not Found */
+            404: {
+                headers: {
+                    /** @description The party this request actually acted for. Present, carrying the organisation identifier, when it acted for an organisation; absent when it acted for your own account. It mirrors the request header, so it can be sent back unchanged. Compare it with what you meant to send: it is the only way to see that a request you meant for an organisation was made personally. */
+                    "X-Broker-Acting-For"?: string;
+                    [name: string]: unknown;
+                };
+                content?: never;
+            };
+        };
+    };
+    RevokeOwnCustomerSessions: {
+        parameters: {
+            query?: never;
+            header?: {
+                /** @description The organisation to act for: one of the identifiers GET /api/v1/customer/contexts lists. Omit it, or send it empty, to act for your own account; there is no mode in which it becomes mandatory. A value you hold no active membership of, or one that is not an organisation identifier, is refused with 403 naming nothing, and never quietly treated as your own account. */
+                "X-Broker-Acting-For"?: components["parameters"]["ActingFor"];
+            };
+            path?: never;
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description OK */
+            200: {
+                headers: {
+                    /** @description The party this request actually acted for. Present, carrying the organisation identifier, when it acted for an organisation; absent when it acted for your own account. It mirrors the request header, so it can be sent back unchanged. Compare it with what you meant to send: it is the only way to see that a request you meant for an organisation was made personally. */
+                    "X-Broker-Acting-For"?: string;
+                    [name: string]: unknown;
+                };
+                content: {
+                    "application/json": components["schemas"]["CustomerSessionRevocationResponse"];
+                };
+            };
+            /** @description Conflict. A type of urn:brokerplatform:problem:concurrency-conflict means someone else changed the record first and nothing was written: read it again and decide again. Any other type is a conflict this operation decided itself, and retrying it unchanged will not help. */
+            409: {
+                headers: {
+                    /** @description The party this request actually acted for. Present, carrying the organisation identifier, when it acted for an organisation; absent when it acted for your own account. It mirrors the request header, so it can be sent back unchanged. Compare it with what you meant to send: it is the only way to see that a request you meant for an organisation was made personally. */
+                    "X-Broker-Acting-For"?: string;
+                    [name: string]: unknown;
+                };
+                content: {
+                    "application/problem+json": components["schemas"]["ConcurrencyConflictProblem"] | components["schemas"]["ProblemDetails"];
+                };
+            };
+        };
+    };
+    RedeemCustomerInvitation: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description OK */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    "application/json": components["schemas"]["RedeemedCustomerAccountResponse"];
+                };
+            };
+            /** @description Conflict. A type of urn:brokerplatform:problem:concurrency-conflict means someone else changed the record first and nothing was written: read it again and decide again. Any other type is a conflict this operation decided itself, and retrying it unchanged will not help. */
+            409: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    "application/problem+json": components["schemas"]["ConcurrencyConflictProblem"] | components["schemas"]["ProblemDetails"];
+                };
+            };
+        };
+    };
     RelabelCustomerVerificationMethod: {
         parameters: {
             query?: never;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@insurance-broker/api-client",
-  "version": "5.50.0",
+  "version": "5.51.0",
   "description": "Generated TypeScript client for the Insurance Broker Platform API. Do not edit by hand: regenerate with scripts/update-api-contract.",
   "license": "UNLICENSED",
   "private": false,