@leaflow/sdk 0.0.0-dev.29.g8fe6a71 → 0.0.0-dev.293.g578f043

package/dist/support/v1/generated/validators/listMaintenanceTimelineParams.zod.d.ts

@@ -0,0 +1,62 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Support API
+ * Support tickets and scheduled maintenance notices.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. The single
+ * exception is `GET /api/v1/notices`, which requires no credentials at all.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Tickets belong to the project
+ *
+ * A ticket is owned by the project it was opened in, not by the person who opened it. Every member
+ * of that project can read it, reply to it and close it. `created_by` records who opened it and is
+ * informational.
+ *
+ * A ticket is in one of three states:
+ *
+ * | State | Meaning |
+ * | --- | --- |
+ * | `OPEN` | Waiting on us |
+ * | `AWAITING_USER` | Waiting on you |
+ * | `CLOSED` | Finished |
+ *
+ * **The state follows whoever spoke last** and cannot be set directly. Posting a message moves the
+ * ticket to `OPEN`; a reply from support moves it to `AWAITING_USER`. Posting a message on a closed
+ * ticket reopens it as `OPEN`, so a follow-up question never lands on a ticket nobody reads.
+ *
+ * Tickets left in `AWAITING_USER` without activity are closed automatically after a period of
+ * inactivity. Tickets in `OPEN` are never closed automatically.
+ *
+ * ## Attachments are uploaded before they are referenced
+ *
+ * Upload a file to `POST /api/v1/attachments`, then pass the returned id in `attachment_ids` when
+ * opening a ticket or posting a message. An attachment that is never referenced is removed after a
+ * time, so upload and reference in the same session.
+ *
+ * The content type is determined from the content itself, not from the `Content-Type` header.
+ * Files whose determined type is not accepted are rejected with `TICKET_ATTACHMENT_TYPE_REJECTED`.
+ *
+ * ## Maintenance is read-only here
+ *
+ * Scheduled maintenance is published by platform operators and is read-only here. Platform
+ * announcements are not part of this API; they are owned by the notification service.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const listMaintenanceTimelineParamsLimitDefault = 50;
+export declare const listMaintenanceTimelineParamsLimitMax = 200;
+export declare const listMaintenanceTimelineParamsOffsetDefault = 0;
+export declare const listMaintenanceTimelineParamsOffsetMin = 0;
+export declare const listMaintenanceTimelineParamsOffsetMax = 10000;
+export declare const ListMaintenanceTimelineParams: zod.ZodObject<{
+    limit: zod.ZodDefault<zod.ZodInt>;
+    offset: zod.ZodDefault<zod.ZodInt>;
+}, zod.z.core.$strict>;
+export type ListMaintenanceTimelineParams = zod.input<typeof ListMaintenanceTimelineParams>;
+export type ListMaintenanceTimelineParamsOutput = zod.output<typeof ListMaintenanceTimelineParams>;

package/dist/support/v1/generated/validators/listMaintenanceTimelineParams.zod.js

@@ -0,0 +1,68 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Support API
+ * Support tickets and scheduled maintenance notices.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. The single
+ * exception is `GET /api/v1/notices`, which requires no credentials at all.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Tickets belong to the project
+ *
+ * A ticket is owned by the project it was opened in, not by the person who opened it. Every member
+ * of that project can read it, reply to it and close it. `created_by` records who opened it and is
+ * informational.
+ *
+ * A ticket is in one of three states:
+ *
+ * | State | Meaning |
+ * | --- | --- |
+ * | `OPEN` | Waiting on us |
+ * | `AWAITING_USER` | Waiting on you |
+ * | `CLOSED` | Finished |
+ *
+ * **The state follows whoever spoke last** and cannot be set directly. Posting a message moves the
+ * ticket to `OPEN`; a reply from support moves it to `AWAITING_USER`. Posting a message on a closed
+ * ticket reopens it as `OPEN`, so a follow-up question never lands on a ticket nobody reads.
+ *
+ * Tickets left in `AWAITING_USER` without activity are closed automatically after a period of
+ * inactivity. Tickets in `OPEN` are never closed automatically.
+ *
+ * ## Attachments are uploaded before they are referenced
+ *
+ * Upload a file to `POST /api/v1/attachments`, then pass the returned id in `attachment_ids` when
+ * opening a ticket or posting a message. An attachment that is never referenced is removed after a
+ * time, so upload and reference in the same session.
+ *
+ * The content type is determined from the content itself, not from the `Content-Type` header.
+ * Files whose determined type is not accepted are rejected with `TICKET_ATTACHMENT_TYPE_REJECTED`.
+ *
+ * ## Maintenance is read-only here
+ *
+ * Scheduled maintenance is published by platform operators and is read-only here. Platform
+ * announcements are not part of this API; they are owned by the notification service.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const listMaintenanceTimelineParamsLimitDefault = 50;
+export const listMaintenanceTimelineParamsLimitMax = 200;
+export const listMaintenanceTimelineParamsOffsetDefault = 0;
+export const listMaintenanceTimelineParamsOffsetMin = 0;
+export const listMaintenanceTimelineParamsOffsetMax = 10000;
+export const ListMaintenanceTimelineParams = zod.strictObject({
+    limit: zod
+        .int()
+        .min(1)
+        .max(listMaintenanceTimelineParamsLimitMax)
+        .default(listMaintenanceTimelineParamsLimitDefault),
+    offset: zod
+        .int()
+        .min(listMaintenanceTimelineParamsOffsetMin)
+        .max(listMaintenanceTimelineParamsOffsetMax)
+        .default(listMaintenanceTimelineParamsOffsetDefault),
+});

package/dist/support/v1/generated/validators/listMaintenancesParams.zod.d.ts

@@ -0,0 +1,70 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Support API
+ * Support tickets and scheduled maintenance notices.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. The single
+ * exception is `GET /api/v1/notices`, which requires no credentials at all.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Tickets belong to the project
+ *
+ * A ticket is owned by the project it was opened in, not by the person who opened it. Every member
+ * of that project can read it, reply to it and close it. `created_by` records who opened it and is
+ * informational.
+ *
+ * A ticket is in one of three states:
+ *
+ * | State | Meaning |
+ * | --- | --- |
+ * | `OPEN` | Waiting on us |
+ * | `AWAITING_USER` | Waiting on you |
+ * | `CLOSED` | Finished |
+ *
+ * **The state follows whoever spoke last** and cannot be set directly. Posting a message moves the
+ * ticket to `OPEN`; a reply from support moves it to `AWAITING_USER`. Posting a message on a closed
+ * ticket reopens it as `OPEN`, so a follow-up question never lands on a ticket nobody reads.
+ *
+ * Tickets left in `AWAITING_USER` without activity are closed automatically after a period of
+ * inactivity. Tickets in `OPEN` are never closed automatically.
+ *
+ * ## Attachments are uploaded before they are referenced
+ *
+ * Upload a file to `POST /api/v1/attachments`, then pass the returned id in `attachment_ids` when
+ * opening a ticket or posting a message. An attachment that is never referenced is removed after a
+ * time, so upload and reference in the same session.
+ *
+ * The content type is determined from the content itself, not from the `Content-Type` header.
+ * Files whose determined type is not accepted are rejected with `TICKET_ATTACHMENT_TYPE_REJECTED`.
+ *
+ * ## Maintenance is read-only here
+ *
+ * Scheduled maintenance is published by platform operators and is read-only here. Platform
+ * announcements are not part of this API; they are owned by the notification service.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const listMaintenancesParamsLimitDefault = 50;
+export declare const listMaintenancesParamsLimitMax = 200;
+export declare const listMaintenancesParamsOffsetDefault = 0;
+export declare const listMaintenancesParamsOffsetMin = 0;
+export declare const listMaintenancesParamsOffsetMax = 10000;
+export declare const listMaintenancesParamsComponentMax = 100;
+export declare const ListMaintenancesParams: zod.ZodObject<{
+    limit: zod.ZodDefault<zod.ZodInt>;
+    offset: zod.ZodDefault<zod.ZodInt>;
+    status: zod.ZodOptional<zod.ZodEnum<{
+        SCHEDULED: "SCHEDULED";
+        IN_PROGRESS: "IN_PROGRESS";
+        COMPLETED: "COMPLETED";
+        CANCELLED: "CANCELLED";
+    }>>;
+    component: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type ListMaintenancesParams = zod.input<typeof ListMaintenancesParams>;
+export type ListMaintenancesParamsOutput = zod.output<typeof ListMaintenancesParams>;

package/dist/support/v1/generated/validators/listMaintenancesParams.zod.js

@@ -0,0 +1,72 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Support API
+ * Support tickets and scheduled maintenance notices.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. The single
+ * exception is `GET /api/v1/notices`, which requires no credentials at all.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Tickets belong to the project
+ *
+ * A ticket is owned by the project it was opened in, not by the person who opened it. Every member
+ * of that project can read it, reply to it and close it. `created_by` records who opened it and is
+ * informational.
+ *
+ * A ticket is in one of three states:
+ *
+ * | State | Meaning |
+ * | --- | --- |
+ * | `OPEN` | Waiting on us |
+ * | `AWAITING_USER` | Waiting on you |
+ * | `CLOSED` | Finished |
+ *
+ * **The state follows whoever spoke last** and cannot be set directly. Posting a message moves the
+ * ticket to `OPEN`; a reply from support moves it to `AWAITING_USER`. Posting a message on a closed
+ * ticket reopens it as `OPEN`, so a follow-up question never lands on a ticket nobody reads.
+ *
+ * Tickets left in `AWAITING_USER` without activity are closed automatically after a period of
+ * inactivity. Tickets in `OPEN` are never closed automatically.
+ *
+ * ## Attachments are uploaded before they are referenced
+ *
+ * Upload a file to `POST /api/v1/attachments`, then pass the returned id in `attachment_ids` when
+ * opening a ticket or posting a message. An attachment that is never referenced is removed after a
+ * time, so upload and reference in the same session.
+ *
+ * The content type is determined from the content itself, not from the `Content-Type` header.
+ * Files whose determined type is not accepted are rejected with `TICKET_ATTACHMENT_TYPE_REJECTED`.
+ *
+ * ## Maintenance is read-only here
+ *
+ * Scheduled maintenance is published by platform operators and is read-only here. Platform
+ * announcements are not part of this API; they are owned by the notification service.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+import { MaintenanceStatus } from "./maintenanceStatus.zod.js";
+export const listMaintenancesParamsLimitDefault = 50;
+export const listMaintenancesParamsLimitMax = 200;
+export const listMaintenancesParamsOffsetDefault = 0;
+export const listMaintenancesParamsOffsetMin = 0;
+export const listMaintenancesParamsOffsetMax = 10000;
+export const listMaintenancesParamsComponentMax = 100;
+export const ListMaintenancesParams = zod.strictObject({
+    limit: zod
+        .int()
+        .min(1)
+        .max(listMaintenancesParamsLimitMax)
+        .default(listMaintenancesParamsLimitDefault),
+    offset: zod
+        .int()
+        .min(listMaintenancesParamsOffsetMin)
+        .max(listMaintenancesParamsOffsetMax)
+        .default(listMaintenancesParamsOffsetDefault),
+    status: MaintenanceStatus.optional(),
+    component: zod.string().max(listMaintenancesParamsComponentMax).optional(),
+});

package/dist/support/v1/generated/validators/listTicketCategoriesParams.zod.d.ts

@@ -0,0 +1,62 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Support API
+ * Support tickets and scheduled maintenance notices.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. The single
+ * exception is `GET /api/v1/notices`, which requires no credentials at all.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Tickets belong to the project
+ *
+ * A ticket is owned by the project it was opened in, not by the person who opened it. Every member
+ * of that project can read it, reply to it and close it. `created_by` records who opened it and is
+ * informational.
+ *
+ * A ticket is in one of three states:
+ *
+ * | State | Meaning |
+ * | --- | --- |
+ * | `OPEN` | Waiting on us |
+ * | `AWAITING_USER` | Waiting on you |
+ * | `CLOSED` | Finished |
+ *
+ * **The state follows whoever spoke last** and cannot be set directly. Posting a message moves the
+ * ticket to `OPEN`; a reply from support moves it to `AWAITING_USER`. Posting a message on a closed
+ * ticket reopens it as `OPEN`, so a follow-up question never lands on a ticket nobody reads.
+ *
+ * Tickets left in `AWAITING_USER` without activity are closed automatically after a period of
+ * inactivity. Tickets in `OPEN` are never closed automatically.
+ *
+ * ## Attachments are uploaded before they are referenced
+ *
+ * Upload a file to `POST /api/v1/attachments`, then pass the returned id in `attachment_ids` when
+ * opening a ticket or posting a message. An attachment that is never referenced is removed after a
+ * time, so upload and reference in the same session.
+ *
+ * The content type is determined from the content itself, not from the `Content-Type` header.
+ * Files whose determined type is not accepted are rejected with `TICKET_ATTACHMENT_TYPE_REJECTED`.
+ *
+ * ## Maintenance is read-only here
+ *
+ * Scheduled maintenance is published by platform operators and is read-only here. Platform
+ * announcements are not part of this API; they are owned by the notification service.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const listTicketCategoriesParamsLimitDefault = 50;
+export declare const listTicketCategoriesParamsLimitMax = 200;
+export declare const listTicketCategoriesParamsOffsetDefault = 0;
+export declare const listTicketCategoriesParamsOffsetMin = 0;
+export declare const listTicketCategoriesParamsOffsetMax = 10000;
+export declare const ListTicketCategoriesParams: zod.ZodObject<{
+    limit: zod.ZodDefault<zod.ZodInt>;
+    offset: zod.ZodDefault<zod.ZodInt>;
+}, zod.z.core.$strict>;
+export type ListTicketCategoriesParams = zod.input<typeof ListTicketCategoriesParams>;
+export type ListTicketCategoriesParamsOutput = zod.output<typeof ListTicketCategoriesParams>;

package/dist/support/v1/generated/validators/listTicketCategoriesParams.zod.js

@@ -0,0 +1,68 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Support API
+ * Support tickets and scheduled maintenance notices.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. The single
+ * exception is `GET /api/v1/notices`, which requires no credentials at all.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Tickets belong to the project
+ *
+ * A ticket is owned by the project it was opened in, not by the person who opened it. Every member
+ * of that project can read it, reply to it and close it. `created_by` records who opened it and is
+ * informational.
+ *
+ * A ticket is in one of three states:
+ *
+ * | State | Meaning |
+ * | --- | --- |
+ * | `OPEN` | Waiting on us |
+ * | `AWAITING_USER` | Waiting on you |
+ * | `CLOSED` | Finished |
+ *
+ * **The state follows whoever spoke last** and cannot be set directly. Posting a message moves the
+ * ticket to `OPEN`; a reply from support moves it to `AWAITING_USER`. Posting a message on a closed
+ * ticket reopens it as `OPEN`, so a follow-up question never lands on a ticket nobody reads.
+ *
+ * Tickets left in `AWAITING_USER` without activity are closed automatically after a period of
+ * inactivity. Tickets in `OPEN` are never closed automatically.
+ *
+ * ## Attachments are uploaded before they are referenced
+ *
+ * Upload a file to `POST /api/v1/attachments`, then pass the returned id in `attachment_ids` when
+ * opening a ticket or posting a message. An attachment that is never referenced is removed after a
+ * time, so upload and reference in the same session.
+ *
+ * The content type is determined from the content itself, not from the `Content-Type` header.
+ * Files whose determined type is not accepted are rejected with `TICKET_ATTACHMENT_TYPE_REJECTED`.
+ *
+ * ## Maintenance is read-only here
+ *
+ * Scheduled maintenance is published by platform operators and is read-only here. Platform
+ * announcements are not part of this API; they are owned by the notification service.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const listTicketCategoriesParamsLimitDefault = 50;
+export const listTicketCategoriesParamsLimitMax = 200;
+export const listTicketCategoriesParamsOffsetDefault = 0;
+export const listTicketCategoriesParamsOffsetMin = 0;
+export const listTicketCategoriesParamsOffsetMax = 10000;
+export const ListTicketCategoriesParams = zod.strictObject({
+    limit: zod
+        .int()
+        .min(1)
+        .max(listTicketCategoriesParamsLimitMax)
+        .default(listTicketCategoriesParamsLimitDefault),
+    offset: zod
+        .int()
+        .min(listTicketCategoriesParamsOffsetMin)
+        .max(listTicketCategoriesParamsOffsetMax)
+        .default(listTicketCategoriesParamsOffsetDefault),
+});

package/dist/support/v1/generated/validators/listTicketMessagesParams.zod.d.ts

@@ -0,0 +1,62 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Support API
+ * Support tickets and scheduled maintenance notices.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. The single
+ * exception is `GET /api/v1/notices`, which requires no credentials at all.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Tickets belong to the project
+ *
+ * A ticket is owned by the project it was opened in, not by the person who opened it. Every member
+ * of that project can read it, reply to it and close it. `created_by` records who opened it and is
+ * informational.
+ *
+ * A ticket is in one of three states:
+ *
+ * | State | Meaning |
+ * | --- | --- |
+ * | `OPEN` | Waiting on us |
+ * | `AWAITING_USER` | Waiting on you |
+ * | `CLOSED` | Finished |
+ *
+ * **The state follows whoever spoke last** and cannot be set directly. Posting a message moves the
+ * ticket to `OPEN`; a reply from support moves it to `AWAITING_USER`. Posting a message on a closed
+ * ticket reopens it as `OPEN`, so a follow-up question never lands on a ticket nobody reads.
+ *
+ * Tickets left in `AWAITING_USER` without activity are closed automatically after a period of
+ * inactivity. Tickets in `OPEN` are never closed automatically.
+ *
+ * ## Attachments are uploaded before they are referenced
+ *
+ * Upload a file to `POST /api/v1/attachments`, then pass the returned id in `attachment_ids` when
+ * opening a ticket or posting a message. An attachment that is never referenced is removed after a
+ * time, so upload and reference in the same session.
+ *
+ * The content type is determined from the content itself, not from the `Content-Type` header.
+ * Files whose determined type is not accepted are rejected with `TICKET_ATTACHMENT_TYPE_REJECTED`.
+ *
+ * ## Maintenance is read-only here
+ *
+ * Scheduled maintenance is published by platform operators and is read-only here. Platform
+ * announcements are not part of this API; they are owned by the notification service.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const listTicketMessagesParamsLimitDefault = 50;
+export declare const listTicketMessagesParamsLimitMax = 200;
+export declare const listTicketMessagesParamsOffsetDefault = 0;
+export declare const listTicketMessagesParamsOffsetMin = 0;
+export declare const listTicketMessagesParamsOffsetMax = 10000;
+export declare const ListTicketMessagesParams: zod.ZodObject<{
+    limit: zod.ZodDefault<zod.ZodInt>;
+    offset: zod.ZodDefault<zod.ZodInt>;
+}, zod.z.core.$strict>;
+export type ListTicketMessagesParams = zod.input<typeof ListTicketMessagesParams>;
+export type ListTicketMessagesParamsOutput = zod.output<typeof ListTicketMessagesParams>;

package/dist/support/v1/generated/validators/listTicketMessagesParams.zod.js

@@ -0,0 +1,68 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Support API
+ * Support tickets and scheduled maintenance notices.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. The single
+ * exception is `GET /api/v1/notices`, which requires no credentials at all.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Tickets belong to the project
+ *
+ * A ticket is owned by the project it was opened in, not by the person who opened it. Every member
+ * of that project can read it, reply to it and close it. `created_by` records who opened it and is
+ * informational.
+ *
+ * A ticket is in one of three states:
+ *
+ * | State | Meaning |
+ * | --- | --- |
+ * | `OPEN` | Waiting on us |
+ * | `AWAITING_USER` | Waiting on you |
+ * | `CLOSED` | Finished |
+ *
+ * **The state follows whoever spoke last** and cannot be set directly. Posting a message moves the
+ * ticket to `OPEN`; a reply from support moves it to `AWAITING_USER`. Posting a message on a closed
+ * ticket reopens it as `OPEN`, so a follow-up question never lands on a ticket nobody reads.
+ *
+ * Tickets left in `AWAITING_USER` without activity are closed automatically after a period of
+ * inactivity. Tickets in `OPEN` are never closed automatically.
+ *
+ * ## Attachments are uploaded before they are referenced
+ *
+ * Upload a file to `POST /api/v1/attachments`, then pass the returned id in `attachment_ids` when
+ * opening a ticket or posting a message. An attachment that is never referenced is removed after a
+ * time, so upload and reference in the same session.
+ *
+ * The content type is determined from the content itself, not from the `Content-Type` header.
+ * Files whose determined type is not accepted are rejected with `TICKET_ATTACHMENT_TYPE_REJECTED`.
+ *
+ * ## Maintenance is read-only here
+ *
+ * Scheduled maintenance is published by platform operators and is read-only here. Platform
+ * announcements are not part of this API; they are owned by the notification service.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const listTicketMessagesParamsLimitDefault = 50;
+export const listTicketMessagesParamsLimitMax = 200;
+export const listTicketMessagesParamsOffsetDefault = 0;
+export const listTicketMessagesParamsOffsetMin = 0;
+export const listTicketMessagesParamsOffsetMax = 10000;
+export const ListTicketMessagesParams = zod.strictObject({
+    limit: zod
+        .int()
+        .min(1)
+        .max(listTicketMessagesParamsLimitMax)
+        .default(listTicketMessagesParamsLimitDefault),
+    offset: zod
+        .int()
+        .min(listTicketMessagesParamsOffsetMin)
+        .max(listTicketMessagesParamsOffsetMax)
+        .default(listTicketMessagesParamsOffsetDefault),
+});

package/dist/support/v1/generated/validators/listTicketsParams.zod.d.ts

@@ -0,0 +1,76 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Support API
+ * Support tickets and scheduled maintenance notices.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. The single
+ * exception is `GET /api/v1/notices`, which requires no credentials at all.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Tickets belong to the project
+ *
+ * A ticket is owned by the project it was opened in, not by the person who opened it. Every member
+ * of that project can read it, reply to it and close it. `created_by` records who opened it and is
+ * informational.
+ *
+ * A ticket is in one of three states:
+ *
+ * | State | Meaning |
+ * | --- | --- |
+ * | `OPEN` | Waiting on us |
+ * | `AWAITING_USER` | Waiting on you |
+ * | `CLOSED` | Finished |
+ *
+ * **The state follows whoever spoke last** and cannot be set directly. Posting a message moves the
+ * ticket to `OPEN`; a reply from support moves it to `AWAITING_USER`. Posting a message on a closed
+ * ticket reopens it as `OPEN`, so a follow-up question never lands on a ticket nobody reads.
+ *
+ * Tickets left in `AWAITING_USER` without activity are closed automatically after a period of
+ * inactivity. Tickets in `OPEN` are never closed automatically.
+ *
+ * ## Attachments are uploaded before they are referenced
+ *
+ * Upload a file to `POST /api/v1/attachments`, then pass the returned id in `attachment_ids` when
+ * opening a ticket or posting a message. An attachment that is never referenced is removed after a
+ * time, so upload and reference in the same session.
+ *
+ * The content type is determined from the content itself, not from the `Content-Type` header.
+ * Files whose determined type is not accepted are rejected with `TICKET_ATTACHMENT_TYPE_REJECTED`.
+ *
+ * ## Maintenance is read-only here
+ *
+ * Scheduled maintenance is published by platform operators and is read-only here. Platform
+ * announcements are not part of this API; they are owned by the notification service.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const listTicketsParamsLimitDefault = 50;
+export declare const listTicketsParamsLimitMax = 200;
+export declare const listTicketsParamsOffsetDefault = 0;
+export declare const listTicketsParamsOffsetMin = 0;
+export declare const listTicketsParamsOffsetMax = 10000;
+export declare const listTicketsParamsKeywordMax = 128;
+export declare const ListTicketsParams: zod.ZodObject<{
+    limit: zod.ZodDefault<zod.ZodInt>;
+    offset: zod.ZodDefault<zod.ZodInt>;
+    status: zod.ZodOptional<zod.ZodEnum<{
+        OPEN: "OPEN";
+        CLOSED: "CLOSED";
+        AWAITING_USER: "AWAITING_USER";
+    }>>;
+    priority: zod.ZodOptional<zod.ZodEnum<{
+        HIGH: "HIGH";
+        LOW: "LOW";
+        NORMAL: "NORMAL";
+        URGENT: "URGENT";
+    }>>;
+    category_id: zod.ZodOptional<zod.ZodUUID>;
+    keyword: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type ListTicketsParams = zod.input<typeof ListTicketsParams>;
+export type ListTicketsParamsOutput = zod.output<typeof ListTicketsParams>;