@wix/auto_sdk_forms_submissions 1.0.149 → 1.0.150
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/build/cjs/{forms-v4-submission-submissions.universal-Bfo2P_8S.d.ts → forms-v4-submission-submissions.universal-DV8oC8Lk.d.ts} +58 -22
- package/build/cjs/index.d.ts +2 -2
- package/build/cjs/index.js.map +1 -1
- package/build/cjs/index.typings.d.ts +2 -2
- package/build/cjs/index.typings.js.map +1 -1
- package/build/cjs/meta.d.ts +58 -22
- package/build/cjs/meta.js.map +1 -1
- package/build/cjs/schemas.js +13 -13
- package/build/cjs/schemas.js.map +1 -1
- package/build/es/{forms-v4-submission-submissions.universal-Bfo2P_8S.d.mts → forms-v4-submission-submissions.universal-DV8oC8Lk.d.mts} +58 -22
- package/build/es/index.d.mts +2 -2
- package/build/es/index.mjs.map +1 -1
- package/build/es/index.typings.d.mts +2 -2
- package/build/es/index.typings.mjs.map +1 -1
- package/build/es/meta.d.mts +58 -22
- package/build/es/meta.mjs.map +1 -1
- package/build/es/schemas.mjs +13 -13
- package/build/es/schemas.mjs.map +1 -1
- package/build/internal/cjs/{forms-v4-submission-submissions.universal-VEnQJRaC.d.ts → forms-v4-submission-submissions.universal-CUKQPm_I.d.ts} +60 -24
- package/build/internal/cjs/index.d.ts +2 -2
- package/build/internal/cjs/index.js.map +1 -1
- package/build/internal/cjs/index.typings.d.ts +2 -2
- package/build/internal/cjs/index.typings.js.map +1 -1
- package/build/internal/cjs/meta.d.ts +60 -24
- package/build/internal/cjs/meta.js.map +1 -1
- package/build/internal/cjs/schemas.js +13 -13
- package/build/internal/cjs/schemas.js.map +1 -1
- package/build/internal/es/{forms-v4-submission-submissions.universal-VEnQJRaC.d.mts → forms-v4-submission-submissions.universal-CUKQPm_I.d.mts} +60 -24
- package/build/internal/es/index.d.mts +2 -2
- package/build/internal/es/index.mjs.map +1 -1
- package/build/internal/es/index.typings.d.mts +2 -2
- package/build/internal/es/index.typings.mjs.map +1 -1
- package/build/internal/es/meta.d.mts +60 -24
- package/build/internal/es/meta.mjs.map +1 -1
- package/build/internal/es/schemas.mjs +13 -13
- package/build/internal/es/schemas.mjs.map +1 -1
- package/package.json +2 -2
package/build/cjs/schemas.js
CHANGED
|
@@ -127,7 +127,7 @@ var CreateSubmissionRequest = z.object({
|
|
|
127
127
|
).min(10).max(50).optional(),
|
|
128
128
|
status: z.enum(["PENDING", "CONFIRMED", "PAYMENT_WAITING", "PAYMENT_CANCELED"]).optional(),
|
|
129
129
|
submissions: z.record(z.string(), z.any()).describe(
|
|
130
|
-
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [Submission
|
|
130
|
+
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [About Submission Values](https://dev.wix.com/docs/api-reference/crm/forms/form-submissions/about-submission-values)."
|
|
131
131
|
).optional(),
|
|
132
132
|
_createdDate: z.date().describe("Date and time the form submission was created.").optional().nullable(),
|
|
133
133
|
_updatedDate: z.date().describe("Date and time the form submission was updated.").optional().nullable(),
|
|
@@ -249,7 +249,7 @@ var CreateSubmissionResponse = z.object({
|
|
|
249
249
|
"Status of the submission.\n\nThe status a submission is created with depends on the form's namespace and on whether the form collects payment, so read it from the response rather than assuming.\n\nA submission for a form that collects payment starts as `PAYMENT_WAITING`. Otherwise, most namespaces record the submission immediately as `CONFIRMED`. Namespaces that need to complete another step first, such as taking payment for a pricing plan, create the submission as `PENDING` and confirm it later with Confirm Submission.\n\nA `PENDING` submission isn't recorded yet, and is deleted automatically if it isn't confirmed in time."
|
|
250
250
|
).optional(),
|
|
251
251
|
submissions: z.record(z.string(), z.any()).describe(
|
|
252
|
-
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [Submission
|
|
252
|
+
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [About Submission Values](https://dev.wix.com/docs/api-reference/crm/forms/form-submissions/about-submission-values)."
|
|
253
253
|
).optional(),
|
|
254
254
|
_createdDate: z.date().describe("Date and time the form submission was created.").optional().nullable(),
|
|
255
255
|
_updatedDate: z.date().describe("Date and time the form submission was updated.").optional().nullable(),
|
|
@@ -370,7 +370,7 @@ var GetSubmissionResponse = z.object({
|
|
|
370
370
|
"Status of the submission.\n\nThe status a submission is created with depends on the form's namespace and on whether the form collects payment, so read it from the response rather than assuming.\n\nA submission for a form that collects payment starts as `PAYMENT_WAITING`. Otherwise, most namespaces record the submission immediately as `CONFIRMED`. Namespaces that need to complete another step first, such as taking payment for a pricing plan, create the submission as `PENDING` and confirm it later with Confirm Submission.\n\nA `PENDING` submission isn't recorded yet, and is deleted automatically if it isn't confirmed in time."
|
|
371
371
|
).optional(),
|
|
372
372
|
submissions: z.record(z.string(), z.any()).describe(
|
|
373
|
-
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [Submission
|
|
373
|
+
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [About Submission Values](https://dev.wix.com/docs/api-reference/crm/forms/form-submissions/about-submission-values)."
|
|
374
374
|
).optional(),
|
|
375
375
|
_createdDate: z.date().describe("Date and time the form submission was created.").optional().nullable(),
|
|
376
376
|
_updatedDate: z.date().describe("Date and time the form submission was updated.").optional().nullable(),
|
|
@@ -488,7 +488,7 @@ var UpdateSubmissionRequest = z.object({
|
|
|
488
488
|
).min(10).max(50).optional(),
|
|
489
489
|
status: z.enum(["PENDING", "CONFIRMED", "PAYMENT_WAITING", "PAYMENT_CANCELED"]).optional(),
|
|
490
490
|
submissions: z.record(z.string(), z.any()).describe(
|
|
491
|
-
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [Submission
|
|
491
|
+
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [About Submission Values](https://dev.wix.com/docs/api-reference/crm/forms/form-submissions/about-submission-values)."
|
|
492
492
|
).optional(),
|
|
493
493
|
_createdDate: z.date().describe("Date and time the form submission was created.").optional().nullable(),
|
|
494
494
|
_updatedDate: z.date().describe("Date and time the form submission was updated.").optional().nullable(),
|
|
@@ -604,7 +604,7 @@ var UpdateSubmissionResponse = z.object({
|
|
|
604
604
|
"Status of the submission.\n\nThe status a submission is created with depends on the form's namespace and on whether the form collects payment, so read it from the response rather than assuming.\n\nA submission for a form that collects payment starts as `PAYMENT_WAITING`. Otherwise, most namespaces record the submission immediately as `CONFIRMED`. Namespaces that need to complete another step first, such as taking payment for a pricing plan, create the submission as `PENDING` and confirm it later with Confirm Submission.\n\nA `PENDING` submission isn't recorded yet, and is deleted automatically if it isn't confirmed in time."
|
|
605
605
|
).optional(),
|
|
606
606
|
submissions: z.record(z.string(), z.any()).describe(
|
|
607
|
-
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [Submission
|
|
607
|
+
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [About Submission Values](https://dev.wix.com/docs/api-reference/crm/forms/form-submissions/about-submission-values)."
|
|
608
608
|
).optional(),
|
|
609
609
|
_createdDate: z.date().describe("Date and time the form submission was created.").optional().nullable(),
|
|
610
610
|
_updatedDate: z.date().describe("Date and time the form submission was updated.").optional().nullable(),
|
|
@@ -726,7 +726,7 @@ var ConfirmSubmissionResponse = z.object({
|
|
|
726
726
|
"Status of the submission.\n\nThe status a submission is created with depends on the form's namespace and on whether the form collects payment, so read it from the response rather than assuming.\n\nA submission for a form that collects payment starts as `PAYMENT_WAITING`. Otherwise, most namespaces record the submission immediately as `CONFIRMED`. Namespaces that need to complete another step first, such as taking payment for a pricing plan, create the submission as `PENDING` and confirm it later with Confirm Submission.\n\nA `PENDING` submission isn't recorded yet, and is deleted automatically if it isn't confirmed in time."
|
|
727
727
|
).optional(),
|
|
728
728
|
submissions: z.record(z.string(), z.any()).describe(
|
|
729
|
-
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [Submission
|
|
729
|
+
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [About Submission Values](https://dev.wix.com/docs/api-reference/crm/forms/form-submissions/about-submission-values)."
|
|
730
730
|
).optional(),
|
|
731
731
|
_createdDate: z.date().describe("Date and time the form submission was created.").optional().nullable(),
|
|
732
732
|
_updatedDate: z.date().describe("Date and time the form submission was updated.").optional().nullable(),
|
|
@@ -907,7 +907,7 @@ var RestoreSubmissionFromTrashBinResponse = z.object({
|
|
|
907
907
|
"Status of the submission.\n\nThe status a submission is created with depends on the form's namespace and on whether the form collects payment, so read it from the response rather than assuming.\n\nA submission for a form that collects payment starts as `PAYMENT_WAITING`. Otherwise, most namespaces record the submission immediately as `CONFIRMED`. Namespaces that need to complete another step first, such as taking payment for a pricing plan, create the submission as `PENDING` and confirm it later with Confirm Submission.\n\nA `PENDING` submission isn't recorded yet, and is deleted automatically if it isn't confirmed in time."
|
|
908
908
|
).optional(),
|
|
909
909
|
submissions: z.record(z.string(), z.any()).describe(
|
|
910
|
-
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [Submission
|
|
910
|
+
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [About Submission Values](https://dev.wix.com/docs/api-reference/crm/forms/form-submissions/about-submission-values)."
|
|
911
911
|
).optional(),
|
|
912
912
|
_createdDate: z.date().describe("Date and time the form submission was created.").optional().nullable(),
|
|
913
913
|
_updatedDate: z.date().describe("Date and time the form submission was updated.").optional().nullable(),
|
|
@@ -1096,7 +1096,7 @@ var ListDeletedSubmissionsResponse = z.object({
|
|
|
1096
1096
|
"Status of the submission.\n\nThe status a submission is created with depends on the form's namespace and on whether the form collects payment, so read it from the response rather than assuming.\n\nA submission for a form that collects payment starts as `PAYMENT_WAITING`. Otherwise, most namespaces record the submission immediately as `CONFIRMED`. Namespaces that need to complete another step first, such as taking payment for a pricing plan, create the submission as `PENDING` and confirm it later with Confirm Submission.\n\nA `PENDING` submission isn't recorded yet, and is deleted automatically if it isn't confirmed in time."
|
|
1097
1097
|
).optional(),
|
|
1098
1098
|
submissions: z.record(z.string(), z.any()).describe(
|
|
1099
|
-
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [Submission
|
|
1099
|
+
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [About Submission Values](https://dev.wix.com/docs/api-reference/crm/forms/form-submissions/about-submission-values)."
|
|
1100
1100
|
).optional(),
|
|
1101
1101
|
_createdDate: z.date().describe("Date and time the form submission was created.").optional().nullable(),
|
|
1102
1102
|
_updatedDate: z.date().describe("Date and time the form submission was updated.").optional().nullable(),
|
|
@@ -1232,7 +1232,7 @@ var GetDeletedSubmissionResponse = z.object({
|
|
|
1232
1232
|
"Status of the submission.\n\nThe status a submission is created with depends on the form's namespace and on whether the form collects payment, so read it from the response rather than assuming.\n\nA submission for a form that collects payment starts as `PAYMENT_WAITING`. Otherwise, most namespaces record the submission immediately as `CONFIRMED`. Namespaces that need to complete another step first, such as taking payment for a pricing plan, create the submission as `PENDING` and confirm it later with Confirm Submission.\n\nA `PENDING` submission isn't recorded yet, and is deleted automatically if it isn't confirmed in time."
|
|
1233
1233
|
).optional(),
|
|
1234
1234
|
submissions: z.record(z.string(), z.any()).describe(
|
|
1235
|
-
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [Submission
|
|
1235
|
+
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [About Submission Values](https://dev.wix.com/docs/api-reference/crm/forms/form-submissions/about-submission-values)."
|
|
1236
1236
|
).optional(),
|
|
1237
1237
|
_createdDate: z.date().describe("Date and time the form submission was created.").optional().nullable(),
|
|
1238
1238
|
_updatedDate: z.date().describe("Date and time the form submission was updated.").optional().nullable(),
|
|
@@ -1383,7 +1383,7 @@ var QuerySubmissionResponse = z.object({
|
|
|
1383
1383
|
"Status of the submission.\n\nThe status a submission is created with depends on the form's namespace and on whether the form collects payment, so read it from the response rather than assuming.\n\nA submission for a form that collects payment starts as `PAYMENT_WAITING`. Otherwise, most namespaces record the submission immediately as `CONFIRMED`. Namespaces that need to complete another step first, such as taking payment for a pricing plan, create the submission as `PENDING` and confirm it later with Confirm Submission.\n\nA `PENDING` submission isn't recorded yet, and is deleted automatically if it isn't confirmed in time."
|
|
1384
1384
|
).optional(),
|
|
1385
1385
|
submissions: z.record(z.string(), z.any()).describe(
|
|
1386
|
-
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [Submission
|
|
1386
|
+
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [About Submission Values](https://dev.wix.com/docs/api-reference/crm/forms/form-submissions/about-submission-values)."
|
|
1387
1387
|
).optional(),
|
|
1388
1388
|
_createdDate: z.date().describe("Date and time the form submission was created.").optional().nullable(),
|
|
1389
1389
|
_updatedDate: z.date().describe("Date and time the form submission was updated.").optional().nullable(),
|
|
@@ -1561,7 +1561,7 @@ var SearchSubmissionsByNamespaceResponse = z.object({
|
|
|
1561
1561
|
"Status of the submission.\n\nThe status a submission is created with depends on the form's namespace and on whether the form collects payment, so read it from the response rather than assuming.\n\nA submission for a form that collects payment starts as `PAYMENT_WAITING`. Otherwise, most namespaces record the submission immediately as `CONFIRMED`. Namespaces that need to complete another step first, such as taking payment for a pricing plan, create the submission as `PENDING` and confirm it later with Confirm Submission.\n\nA `PENDING` submission isn't recorded yet, and is deleted automatically if it isn't confirmed in time."
|
|
1562
1562
|
).optional(),
|
|
1563
1563
|
submissions: z.record(z.string(), z.any()).describe(
|
|
1564
|
-
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [Submission
|
|
1564
|
+
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [About Submission Values](https://dev.wix.com/docs/api-reference/crm/forms/form-submissions/about-submission-values)."
|
|
1565
1565
|
).optional(),
|
|
1566
1566
|
_createdDate: z.date().describe("Date and time the form submission was created.").optional().nullable(),
|
|
1567
1567
|
_updatedDate: z.date().describe("Date and time the form submission was updated.").optional().nullable(),
|
|
@@ -1804,7 +1804,7 @@ var QuerySubmissionsByNamespaceResponse = z.object({
|
|
|
1804
1804
|
"Status of the submission.\n\nThe status a submission is created with depends on the form's namespace and on whether the form collects payment, so read it from the response rather than assuming.\n\nA submission for a form that collects payment starts as `PAYMENT_WAITING`. Otherwise, most namespaces record the submission immediately as `CONFIRMED`. Namespaces that need to complete another step first, such as taking payment for a pricing plan, create the submission as `PENDING` and confirm it later with Confirm Submission.\n\nA `PENDING` submission isn't recorded yet, and is deleted automatically if it isn't confirmed in time."
|
|
1805
1805
|
).optional(),
|
|
1806
1806
|
submissions: z.record(z.string(), z.any()).describe(
|
|
1807
|
-
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [Submission
|
|
1807
|
+
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [About Submission Values](https://dev.wix.com/docs/api-reference/crm/forms/form-submissions/about-submission-values)."
|
|
1808
1808
|
).optional(),
|
|
1809
1809
|
_createdDate: z.date().describe("Date and time the form submission was created.").optional().nullable(),
|
|
1810
1810
|
_updatedDate: z.date().describe("Date and time the form submission was updated.").optional().nullable(),
|
|
@@ -2115,7 +2115,7 @@ var ValidateFormSubmissionRequest = z.object({
|
|
|
2115
2115
|
).min(10).max(50).optional(),
|
|
2116
2116
|
status: z.enum(["PENDING", "CONFIRMED", "PAYMENT_WAITING", "PAYMENT_CANCELED"]).optional(),
|
|
2117
2117
|
submissions: z.record(z.string(), z.any()).describe(
|
|
2118
|
-
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [Submission
|
|
2118
|
+
"Values the visitor submitted.\n\nEach key is the `target` of a field in the form schema, which is the field's stable storage key rather than its ID or label. Only keys matching a field target are accepted.\n\nEach value's shape follows that field's `inputType`: `STRING` fields submit a string, `NUMBER` a number, `BOOLEAN` a boolean, and `ARRAY` an array of the selected option values. Date and time fields are strings.\n\n3 input types submit structured values: `ADDRESS` submits an address object, `PAYMENT` an array holding 1 product object per item bought, and `SCHEDULING` an appointment object.\n\nFor the full mapping, see [About Submission Values](https://dev.wix.com/docs/api-reference/crm/forms/form-submissions/about-submission-values)."
|
|
2119
2119
|
).optional(),
|
|
2120
2120
|
_createdDate: z.date().describe("Date and time the form submission was created.").optional().nullable(),
|
|
2121
2121
|
_updatedDate: z.date().describe("Date and time the form submission was updated.").optional().nullable(),
|