@wix/auto_sdk_online-programs_programs 1.0.25 → 1.0.27
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/index.d.ts +2 -2
- package/build/cjs/index.js +4 -7
- package/build/cjs/index.js.map +1 -1
- package/build/cjs/index.typings.d.ts +2 -2
- package/build/cjs/index.typings.js +3 -6
- package/build/cjs/index.typings.js.map +1 -1
- package/build/cjs/meta.d.ts +24 -3
- package/build/cjs/meta.js +1 -0
- package/build/cjs/meta.js.map +1 -1
- package/build/cjs/{online-programs-v3-program-programs.universal-BkiNXEkh.d.ts → online-programs-v3-program-programs.universal-DHoODqUk.d.ts} +25 -17
- package/build/cjs/schemas.js +54 -54
- package/build/cjs/schemas.js.map +1 -1
- package/build/es/index.d.mts +2 -2
- package/build/es/index.mjs +4 -7
- package/build/es/index.mjs.map +1 -1
- package/build/es/index.typings.d.mts +2 -2
- package/build/es/index.typings.mjs +3 -6
- package/build/es/index.typings.mjs.map +1 -1
- package/build/es/meta.d.mts +24 -3
- package/build/es/meta.mjs +1 -0
- package/build/es/meta.mjs.map +1 -1
- package/build/es/{online-programs-v3-program-programs.universal-BkiNXEkh.d.mts → online-programs-v3-program-programs.universal-DHoODqUk.d.mts} +25 -17
- package/build/es/schemas.mjs +54 -54
- package/build/es/schemas.mjs.map +1 -1
- package/build/internal/cjs/index.d.ts +2 -2
- package/build/internal/cjs/index.js +4 -7
- 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 +3 -6
- package/build/internal/cjs/index.typings.js.map +1 -1
- package/build/internal/cjs/meta.d.ts +24 -3
- package/build/internal/cjs/meta.js +1 -0
- package/build/internal/cjs/meta.js.map +1 -1
- package/build/internal/cjs/{online-programs-v3-program-programs.universal-D5nSylw5.d.ts → online-programs-v3-program-programs.universal-CauvIR3y.d.ts} +25 -17
- package/build/internal/cjs/schemas.js +54 -54
- package/build/internal/cjs/schemas.js.map +1 -1
- package/build/internal/es/index.d.mts +2 -2
- package/build/internal/es/index.mjs +4 -7
- 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 +3 -6
- package/build/internal/es/index.typings.mjs.map +1 -1
- package/build/internal/es/meta.d.mts +24 -3
- package/build/internal/es/meta.mjs +1 -0
- package/build/internal/es/meta.mjs.map +1 -1
- package/build/internal/es/{online-programs-v3-program-programs.universal-D5nSylw5.d.mts → online-programs-v3-program-programs.universal-CauvIR3y.d.mts} +25 -17
- package/build/internal/es/schemas.mjs +54 -54
- package/build/internal/es/schemas.mjs.map +1 -1
- package/package.json +3 -3
|
@@ -253,6 +253,13 @@ interface Tag {
|
|
|
253
253
|
*
|
|
254
254
|
*
|
|
255
255
|
* Supported values: `title`, `meta`, `script`, `link`.
|
|
256
|
+
*
|
|
257
|
+
* Which of these an API actually accepts depends on where the tag is being set: this
|
|
258
|
+
* list is not a blanket guarantee across every API that reuses this message. Site SEO
|
|
259
|
+
* Tags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects
|
|
260
|
+
* `title`/`script`/`link` with a validation error even though they appear here —
|
|
261
|
+
* check the field description of the specific `tags`-typed field you're writing to
|
|
262
|
+
* for the types it actually supports and the error it returns.
|
|
256
263
|
*/
|
|
257
264
|
type?: string;
|
|
258
265
|
/**
|
|
@@ -268,6 +275,12 @@ interface Tag {
|
|
|
268
275
|
* Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) —
|
|
269
276
|
* i.e. an entry from the site's Advanced/Custom Tags list.
|
|
270
277
|
*
|
|
278
|
+
* Note this is a separate restriction from Site SEO Tags' own type restriction on
|
|
279
|
+
* `SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.
|
|
280
|
+
* for site-wide structured data) unconditionally. There is currently no way to set
|
|
281
|
+
* site-wide, every-page structured data through any of these APIs — write a per-page
|
|
282
|
+
* `script` tag through the Item SEO Tags API instead.
|
|
283
|
+
*
|
|
271
284
|
* This flag is scoped to that feature only. It is NOT an indicator of whether a standard tag
|
|
272
285
|
* (`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed
|
|
273
286
|
* default/pattern — standard tags always resolve with `custom: false`, even when their content comes
|
|
@@ -1943,10 +1956,18 @@ declare enum Namespace {
|
|
|
1943
1956
|
* (theme, typography, assets) which is rolled out to the BrandKit's connected sites.
|
|
1944
1957
|
* MetaSites with this namespace will *not* be shown in a user's site list by default.
|
|
1945
1958
|
*/
|
|
1946
|
-
ENTERPRISE_BRAND_KIT = "ENTERPRISE_BRAND_KIT"
|
|
1959
|
+
ENTERPRISE_BRAND_KIT = "ENTERPRISE_BRAND_KIT",
|
|
1960
|
+
/**
|
|
1961
|
+
* Development sites managed by dev-center's DevelopmentSitesManager (com.wixpress.devcenter.dsm) —
|
|
1962
|
+
* real, fully premium Wix sites created from a template and lent to a developer to test their
|
|
1963
|
+
* in-development app. Distinct from DEV_SITE (Wix Blocks app-backing sites keyed by app_def_id).
|
|
1964
|
+
* Owner: ot-dev-center-platform.
|
|
1965
|
+
* MetaSites with this namespace will *not* be shown in a user's site list by default.
|
|
1966
|
+
*/
|
|
1967
|
+
DEV_CENTER_DEV_SITE = "DEV_CENTER_DEV_SITE"
|
|
1947
1968
|
}
|
|
1948
1969
|
/** @enumType */
|
|
1949
|
-
type NamespaceWithLiterals = Namespace | 'UNKNOWN_NAMESPACE' | 'WIX' | 'SHOUT_OUT' | 'ALBUMS' | 'WIX_STORES_TEST_DRIVE' | 'HOTELS' | 'CLUBS' | 'ONBOARDING_DRAFT' | 'DEV_SITE' | 'LOGOS' | 'VIDEO_MAKER' | 'PARTNER_DASHBOARD' | 'DEV_CENTER_COMPANY' | 'HTML_DRAFT' | 'SITELESS_BUSINESS' | 'CREATOR_ECONOMY' | 'DASHBOARD_FIRST' | 'ANYWHERE' | 'HEADLESS' | 'ACCOUNT_MASTER_CMS' | 'RISE' | 'BRANDED_FIRST' | 'NOWNIA' | 'UGC_TEMPLATE' | 'CODUX' | 'MEDIA_DESIGN_CREATOR' | 'SHARED_BLOG_ENTERPRISE' | 'STANDALONE_FORMS' | 'STANDALONE_EVENTS' | 'MIMIR' | 'TWINS' | 'NANO' | 'BASE44' | 'CHANNELS' | 'NAUTILUS' | 'SYMPHONY' | 'NAUTILUS_APPS' | 'VIBU' | 'ENTERPRISE_BRAND_KIT';
|
|
1970
|
+
type NamespaceWithLiterals = Namespace | 'UNKNOWN_NAMESPACE' | 'WIX' | 'SHOUT_OUT' | 'ALBUMS' | 'WIX_STORES_TEST_DRIVE' | 'HOTELS' | 'CLUBS' | 'ONBOARDING_DRAFT' | 'DEV_SITE' | 'LOGOS' | 'VIDEO_MAKER' | 'PARTNER_DASHBOARD' | 'DEV_CENTER_COMPANY' | 'HTML_DRAFT' | 'SITELESS_BUSINESS' | 'CREATOR_ECONOMY' | 'DASHBOARD_FIRST' | 'ANYWHERE' | 'HEADLESS' | 'ACCOUNT_MASTER_CMS' | 'RISE' | 'BRANDED_FIRST' | 'NOWNIA' | 'UGC_TEMPLATE' | 'CODUX' | 'MEDIA_DESIGN_CREATOR' | 'SHARED_BLOG_ENTERPRISE' | 'STANDALONE_FORMS' | 'STANDALONE_EVENTS' | 'MIMIR' | 'TWINS' | 'NANO' | 'BASE44' | 'CHANNELS' | 'NAUTILUS' | 'SYMPHONY' | 'NAUTILUS_APPS' | 'VIBU' | 'ENTERPRISE_BRAND_KIT' | 'DEV_CENTER_DEV_SITE';
|
|
1950
1971
|
/** Site transferred to another user. */
|
|
1951
1972
|
interface SiteTransferred {
|
|
1952
1973
|
/**
|
|
@@ -2875,21 +2896,8 @@ type ProgramQuery = {
|
|
|
2875
2896
|
}[];
|
|
2876
2897
|
};
|
|
2877
2898
|
declare const utils: {
|
|
2878
|
-
query:
|
|
2879
|
-
|
|
2880
|
-
Filter: _wix_sdk_types.FilterFactory<Program, ProgramQuerySpec>;
|
|
2881
|
-
Sort: _wix_sdk_types.SortFactory<ProgramQuerySpec>; /**
|
|
2882
|
-
* List of nested aggregations.
|
|
2883
|
-
* @maxSize 1000
|
|
2884
|
-
*/
|
|
2885
|
-
};
|
|
2886
|
-
search: {
|
|
2887
|
-
SearchBuilder: () => _wix_sdk_types.SearchBuilder<Program, ProgramSearchSpec, ProgramSearch>;
|
|
2888
|
-
Filter: _wix_sdk_types.FilterFactory<Program, ProgramSearchSpec>;
|
|
2889
|
-
Sort: _wix_sdk_types.SortFactory<ProgramSearchSpec>;
|
|
2890
|
-
SearchParams: _wix_sdk_types.SearchParamsFactory<ProgramSearchSpec>;
|
|
2891
|
-
Aggregation: _wix_sdk_types.AggregationFactory<ProgramSearchSpec>;
|
|
2892
|
-
};
|
|
2899
|
+
query: _wix_sdk_types.QueryHelpers<Program, ProgramQuerySpec, ProgramQuery>;
|
|
2900
|
+
search: _wix_sdk_types.SearchHelpers<Program, ProgramSearchSpec, ProgramSearch>;
|
|
2893
2901
|
};
|
|
2894
2902
|
interface ProgramSearchSpec extends SearchSpec {
|
|
2895
2903
|
searchable: ['description.title'];
|
package/build/cjs/schemas.js
CHANGED
|
@@ -61,7 +61,7 @@ module.exports = __toCommonJS(schemas_exports);
|
|
|
61
61
|
|
|
62
62
|
// src/online-programs-v3-program-programs.schemas.ts
|
|
63
63
|
var z = __toESM(require("zod"));
|
|
64
|
-
var CreateProgramRequest = z.object({
|
|
64
|
+
var CreateProgramRequest = /* @__PURE__ */ z.object({
|
|
65
65
|
program: z.object({
|
|
66
66
|
_id: z.string().describe("Program ID.").regex(
|
|
67
67
|
/^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
|
|
@@ -129,7 +129,7 @@ var CreateProgramRequest = z.object({
|
|
|
129
129
|
tags: z.array(
|
|
130
130
|
z.object({
|
|
131
131
|
type: z.string().describe(
|
|
132
|
-
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link
|
|
132
|
+
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
|
|
133
133
|
).optional(),
|
|
134
134
|
props: z.record(z.string(), z.any()).describe(
|
|
135
135
|
'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
|
|
@@ -141,7 +141,7 @@ var CreateProgramRequest = z.object({
|
|
|
141
141
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
142
142
|
).optional(),
|
|
143
143
|
custom: z.boolean().describe(
|
|
144
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
144
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
145
145
|
).optional(),
|
|
146
146
|
disabled: z.boolean().describe(
|
|
147
147
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -229,7 +229,7 @@ var CreateProgramRequest = z.object({
|
|
|
229
229
|
"Program to create. Server-generated fields such as `id`, `revision`, status, dates, owner, and content summary are ignored on create."
|
|
230
230
|
)
|
|
231
231
|
});
|
|
232
|
-
var CreateProgramResponse = z.object({
|
|
232
|
+
var CreateProgramResponse = /* @__PURE__ */ z.object({
|
|
233
233
|
_id: z.string().describe("Program ID.").regex(
|
|
234
234
|
/^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
|
|
235
235
|
"Must be a valid GUID"
|
|
@@ -293,7 +293,7 @@ var CreateProgramResponse = z.object({
|
|
|
293
293
|
tags: z.array(
|
|
294
294
|
z.object({
|
|
295
295
|
type: z.string().describe(
|
|
296
|
-
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link
|
|
296
|
+
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
|
|
297
297
|
).optional(),
|
|
298
298
|
props: z.record(z.string(), z.any()).describe(
|
|
299
299
|
'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
|
|
@@ -305,7 +305,7 @@ var CreateProgramResponse = z.object({
|
|
|
305
305
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
306
306
|
).optional(),
|
|
307
307
|
custom: z.boolean().describe(
|
|
308
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
308
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
309
309
|
).optional(),
|
|
310
310
|
disabled: z.boolean().describe(
|
|
311
311
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -382,13 +382,13 @@ var CreateProgramResponse = z.object({
|
|
|
382
382
|
"Must be a valid GUID"
|
|
383
383
|
).optional().nullable()
|
|
384
384
|
});
|
|
385
|
-
var DuplicateProgramRequest = z.object({
|
|
385
|
+
var DuplicateProgramRequest = /* @__PURE__ */ z.object({
|
|
386
386
|
programId: z.string().describe("ID of the program to duplicate.").regex(
|
|
387
387
|
/^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
|
|
388
388
|
"Must be a valid GUID"
|
|
389
389
|
)
|
|
390
390
|
});
|
|
391
|
-
var DuplicateProgramResponse = z.object({
|
|
391
|
+
var DuplicateProgramResponse = /* @__PURE__ */ z.object({
|
|
392
392
|
program: z.object({
|
|
393
393
|
_id: z.string().describe("Program ID.").regex(
|
|
394
394
|
/^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
|
|
@@ -456,7 +456,7 @@ var DuplicateProgramResponse = z.object({
|
|
|
456
456
|
tags: z.array(
|
|
457
457
|
z.object({
|
|
458
458
|
type: z.string().describe(
|
|
459
|
-
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link
|
|
459
|
+
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
|
|
460
460
|
).optional(),
|
|
461
461
|
props: z.record(z.string(), z.any()).describe(
|
|
462
462
|
'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
|
|
@@ -468,7 +468,7 @@ var DuplicateProgramResponse = z.object({
|
|
|
468
468
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
469
469
|
).optional(),
|
|
470
470
|
custom: z.boolean().describe(
|
|
471
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
471
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
472
472
|
).optional(),
|
|
473
473
|
disabled: z.boolean().describe(
|
|
474
474
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -556,13 +556,13 @@ var DuplicateProgramResponse = z.object({
|
|
|
556
556
|
).optional().nullable()
|
|
557
557
|
}).describe("New draft program created from the source program.").optional()
|
|
558
558
|
});
|
|
559
|
-
var GetProgramRequest = z.object({
|
|
559
|
+
var GetProgramRequest = /* @__PURE__ */ z.object({
|
|
560
560
|
programId: z.string().describe("ID of the program to retrieve.").regex(
|
|
561
561
|
/^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
|
|
562
562
|
"Must be a valid GUID"
|
|
563
563
|
)
|
|
564
564
|
});
|
|
565
|
-
var GetProgramResponse = z.object({
|
|
565
|
+
var GetProgramResponse = /* @__PURE__ */ z.object({
|
|
566
566
|
_id: z.string().describe("Program ID.").regex(
|
|
567
567
|
/^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
|
|
568
568
|
"Must be a valid GUID"
|
|
@@ -626,7 +626,7 @@ var GetProgramResponse = z.object({
|
|
|
626
626
|
tags: z.array(
|
|
627
627
|
z.object({
|
|
628
628
|
type: z.string().describe(
|
|
629
|
-
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link
|
|
629
|
+
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
|
|
630
630
|
).optional(),
|
|
631
631
|
props: z.record(z.string(), z.any()).describe(
|
|
632
632
|
'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
|
|
@@ -638,7 +638,7 @@ var GetProgramResponse = z.object({
|
|
|
638
638
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
639
639
|
).optional(),
|
|
640
640
|
custom: z.boolean().describe(
|
|
641
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
641
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
642
642
|
).optional(),
|
|
643
643
|
disabled: z.boolean().describe(
|
|
644
644
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -715,7 +715,7 @@ var GetProgramResponse = z.object({
|
|
|
715
715
|
"Must be a valid GUID"
|
|
716
716
|
).optional().nullable()
|
|
717
717
|
});
|
|
718
|
-
var UpdateProgramRequest = z.object({
|
|
718
|
+
var UpdateProgramRequest = /* @__PURE__ */ z.object({
|
|
719
719
|
_id: z.string().describe("Program ID.").regex(
|
|
720
720
|
/^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
|
|
721
721
|
"Must be a valid GUID"
|
|
@@ -787,7 +787,7 @@ var UpdateProgramRequest = z.object({
|
|
|
787
787
|
tags: z.array(
|
|
788
788
|
z.object({
|
|
789
789
|
type: z.string().describe(
|
|
790
|
-
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link
|
|
790
|
+
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
|
|
791
791
|
).optional(),
|
|
792
792
|
props: z.record(z.string(), z.any()).describe(
|
|
793
793
|
'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
|
|
@@ -799,7 +799,7 @@ var UpdateProgramRequest = z.object({
|
|
|
799
799
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
800
800
|
).optional(),
|
|
801
801
|
custom: z.boolean().describe(
|
|
802
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
802
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
803
803
|
).optional(),
|
|
804
804
|
disabled: z.boolean().describe(
|
|
805
805
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -887,7 +887,7 @@ var UpdateProgramRequest = z.object({
|
|
|
887
887
|
"Program fields to update. Include `id` and the latest `revision`."
|
|
888
888
|
)
|
|
889
889
|
});
|
|
890
|
-
var UpdateProgramResponse = z.object({
|
|
890
|
+
var UpdateProgramResponse = /* @__PURE__ */ z.object({
|
|
891
891
|
_id: z.string().describe("Program ID.").regex(
|
|
892
892
|
/^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
|
|
893
893
|
"Must be a valid GUID"
|
|
@@ -951,7 +951,7 @@ var UpdateProgramResponse = z.object({
|
|
|
951
951
|
tags: z.array(
|
|
952
952
|
z.object({
|
|
953
953
|
type: z.string().describe(
|
|
954
|
-
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link
|
|
954
|
+
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
|
|
955
955
|
).optional(),
|
|
956
956
|
props: z.record(z.string(), z.any()).describe(
|
|
957
957
|
'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
|
|
@@ -963,7 +963,7 @@ var UpdateProgramResponse = z.object({
|
|
|
963
963
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
964
964
|
).optional(),
|
|
965
965
|
custom: z.boolean().describe(
|
|
966
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
966
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
967
967
|
).optional(),
|
|
968
968
|
disabled: z.boolean().describe(
|
|
969
969
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -1040,14 +1040,14 @@ var UpdateProgramResponse = z.object({
|
|
|
1040
1040
|
"Must be a valid GUID"
|
|
1041
1041
|
).optional().nullable()
|
|
1042
1042
|
});
|
|
1043
|
-
var DeleteProgramRequest = z.object({
|
|
1043
|
+
var DeleteProgramRequest = /* @__PURE__ */ z.object({
|
|
1044
1044
|
programId: z.string().describe("ID of the program to delete.").regex(
|
|
1045
1045
|
/^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
|
|
1046
1046
|
"Must be a valid GUID"
|
|
1047
1047
|
)
|
|
1048
1048
|
});
|
|
1049
|
-
var DeleteProgramResponse = z.object({});
|
|
1050
|
-
var QueryProgramsRequest = z.object({
|
|
1049
|
+
var DeleteProgramResponse = /* @__PURE__ */ z.object({});
|
|
1050
|
+
var QueryProgramsRequest = /* @__PURE__ */ z.object({
|
|
1051
1051
|
query: z.intersection(
|
|
1052
1052
|
z.object({
|
|
1053
1053
|
filter: z.record(z.string(), z.any()).describe(
|
|
@@ -1086,7 +1086,7 @@ var QueryProgramsRequest = z.object({
|
|
|
1086
1086
|
])
|
|
1087
1087
|
).describe("Query used to filter, sort, and page programs.")
|
|
1088
1088
|
});
|
|
1089
|
-
var QueryProgramsResponse = z.object({
|
|
1089
|
+
var QueryProgramsResponse = /* @__PURE__ */ z.object({
|
|
1090
1090
|
programs: z.array(
|
|
1091
1091
|
z.object({
|
|
1092
1092
|
_id: z.string().describe("Program ID.").regex(
|
|
@@ -1155,7 +1155,7 @@ var QueryProgramsResponse = z.object({
|
|
|
1155
1155
|
tags: z.array(
|
|
1156
1156
|
z.object({
|
|
1157
1157
|
type: z.string().describe(
|
|
1158
|
-
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link
|
|
1158
|
+
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
|
|
1159
1159
|
).optional(),
|
|
1160
1160
|
props: z.record(z.string(), z.any()).describe(
|
|
1161
1161
|
'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
|
|
@@ -1167,7 +1167,7 @@ var QueryProgramsResponse = z.object({
|
|
|
1167
1167
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
1168
1168
|
).optional(),
|
|
1169
1169
|
custom: z.boolean().describe(
|
|
1170
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
1170
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
1171
1171
|
).optional(),
|
|
1172
1172
|
disabled: z.boolean().describe(
|
|
1173
1173
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -1276,7 +1276,7 @@ var QueryProgramsResponse = z.object({
|
|
|
1276
1276
|
).optional()
|
|
1277
1277
|
}).describe("Paging metadata for the query response.").optional()
|
|
1278
1278
|
});
|
|
1279
|
-
var SearchProgramsRequest = z.object({
|
|
1279
|
+
var SearchProgramsRequest = /* @__PURE__ */ z.object({
|
|
1280
1280
|
search: z.intersection(
|
|
1281
1281
|
z.object({
|
|
1282
1282
|
filter: z.record(z.string(), z.any()).describe(
|
|
@@ -1580,7 +1580,7 @@ var SearchProgramsRequest = z.object({
|
|
|
1580
1580
|
"Search expression, filters, sorting, and cursor paging options."
|
|
1581
1581
|
)
|
|
1582
1582
|
});
|
|
1583
|
-
var SearchProgramsResponse = z.object({
|
|
1583
|
+
var SearchProgramsResponse = /* @__PURE__ */ z.object({
|
|
1584
1584
|
programs: z.array(
|
|
1585
1585
|
z.object({
|
|
1586
1586
|
_id: z.string().describe("Program ID.").regex(
|
|
@@ -1649,7 +1649,7 @@ var SearchProgramsResponse = z.object({
|
|
|
1649
1649
|
tags: z.array(
|
|
1650
1650
|
z.object({
|
|
1651
1651
|
type: z.string().describe(
|
|
1652
|
-
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link
|
|
1652
|
+
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
|
|
1653
1653
|
).optional(),
|
|
1654
1654
|
props: z.record(z.string(), z.any()).describe(
|
|
1655
1655
|
'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
|
|
@@ -1661,7 +1661,7 @@ var SearchProgramsResponse = z.object({
|
|
|
1661
1661
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
1662
1662
|
).optional(),
|
|
1663
1663
|
custom: z.boolean().describe(
|
|
1664
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
1664
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
1665
1665
|
).optional(),
|
|
1666
1666
|
disabled: z.boolean().describe(
|
|
1667
1667
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -2010,13 +2010,13 @@ var SearchProgramsResponse = z.object({
|
|
|
2010
2010
|
).max(1e4).optional()
|
|
2011
2011
|
}).describe("Aggregation data returned by the search backend.").optional()
|
|
2012
2012
|
});
|
|
2013
|
-
var PublishProgramRequest = z.object({
|
|
2013
|
+
var PublishProgramRequest = /* @__PURE__ */ z.object({
|
|
2014
2014
|
programId: z.string().describe("ID of the draft program to publish.").regex(
|
|
2015
2015
|
/^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
|
|
2016
2016
|
"Must be a valid GUID"
|
|
2017
2017
|
)
|
|
2018
2018
|
});
|
|
2019
|
-
var PublishProgramResponse = z.object({
|
|
2019
|
+
var PublishProgramResponse = /* @__PURE__ */ z.object({
|
|
2020
2020
|
program: z.object({
|
|
2021
2021
|
_id: z.string().describe("Program ID.").regex(
|
|
2022
2022
|
/^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
|
|
@@ -2084,7 +2084,7 @@ var PublishProgramResponse = z.object({
|
|
|
2084
2084
|
tags: z.array(
|
|
2085
2085
|
z.object({
|
|
2086
2086
|
type: z.string().describe(
|
|
2087
|
-
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link
|
|
2087
|
+
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
|
|
2088
2088
|
).optional(),
|
|
2089
2089
|
props: z.record(z.string(), z.any()).describe(
|
|
2090
2090
|
'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
|
|
@@ -2096,7 +2096,7 @@ var PublishProgramResponse = z.object({
|
|
|
2096
2096
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
2097
2097
|
).optional(),
|
|
2098
2098
|
custom: z.boolean().describe(
|
|
2099
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
2099
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
2100
2100
|
).optional(),
|
|
2101
2101
|
disabled: z.boolean().describe(
|
|
2102
2102
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -2184,13 +2184,13 @@ var PublishProgramResponse = z.object({
|
|
|
2184
2184
|
).optional().nullable()
|
|
2185
2185
|
}).describe("Published program.").optional()
|
|
2186
2186
|
});
|
|
2187
|
-
var EndProgramRequest = z.object({
|
|
2187
|
+
var EndProgramRequest = /* @__PURE__ */ z.object({
|
|
2188
2188
|
programId: z.string().describe("ID of the published program to end.").regex(
|
|
2189
2189
|
/^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
|
|
2190
2190
|
"Must be a valid GUID"
|
|
2191
2191
|
)
|
|
2192
2192
|
});
|
|
2193
|
-
var EndProgramResponse = z.object({
|
|
2193
|
+
var EndProgramResponse = /* @__PURE__ */ z.object({
|
|
2194
2194
|
program: z.object({
|
|
2195
2195
|
_id: z.string().describe("Program ID.").regex(
|
|
2196
2196
|
/^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
|
|
@@ -2258,7 +2258,7 @@ var EndProgramResponse = z.object({
|
|
|
2258
2258
|
tags: z.array(
|
|
2259
2259
|
z.object({
|
|
2260
2260
|
type: z.string().describe(
|
|
2261
|
-
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link
|
|
2261
|
+
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
|
|
2262
2262
|
).optional(),
|
|
2263
2263
|
props: z.record(z.string(), z.any()).describe(
|
|
2264
2264
|
'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
|
|
@@ -2270,7 +2270,7 @@ var EndProgramResponse = z.object({
|
|
|
2270
2270
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
2271
2271
|
).optional(),
|
|
2272
2272
|
custom: z.boolean().describe(
|
|
2273
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
2273
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
2274
2274
|
).optional(),
|
|
2275
2275
|
disabled: z.boolean().describe(
|
|
2276
2276
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -2358,13 +2358,13 @@ var EndProgramResponse = z.object({
|
|
|
2358
2358
|
).optional().nullable()
|
|
2359
2359
|
}).describe("Ended program.").optional()
|
|
2360
2360
|
});
|
|
2361
|
-
var ArchiveProgramRequest = z.object({
|
|
2361
|
+
var ArchiveProgramRequest = /* @__PURE__ */ z.object({
|
|
2362
2362
|
programId: z.string().describe("ID of the program to archive.").regex(
|
|
2363
2363
|
/^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
|
|
2364
2364
|
"Must be a valid GUID"
|
|
2365
2365
|
)
|
|
2366
2366
|
});
|
|
2367
|
-
var ArchiveProgramResponse = z.object({
|
|
2367
|
+
var ArchiveProgramResponse = /* @__PURE__ */ z.object({
|
|
2368
2368
|
program: z.object({
|
|
2369
2369
|
_id: z.string().describe("Program ID.").regex(
|
|
2370
2370
|
/^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
|
|
@@ -2432,7 +2432,7 @@ var ArchiveProgramResponse = z.object({
|
|
|
2432
2432
|
tags: z.array(
|
|
2433
2433
|
z.object({
|
|
2434
2434
|
type: z.string().describe(
|
|
2435
|
-
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link
|
|
2435
|
+
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
|
|
2436
2436
|
).optional(),
|
|
2437
2437
|
props: z.record(z.string(), z.any()).describe(
|
|
2438
2438
|
'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
|
|
@@ -2444,7 +2444,7 @@ var ArchiveProgramResponse = z.object({
|
|
|
2444
2444
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
2445
2445
|
).optional(),
|
|
2446
2446
|
custom: z.boolean().describe(
|
|
2447
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
2447
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
2448
2448
|
).optional(),
|
|
2449
2449
|
disabled: z.boolean().describe(
|
|
2450
2450
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -2532,7 +2532,7 @@ var ArchiveProgramResponse = z.object({
|
|
|
2532
2532
|
).optional().nullable()
|
|
2533
2533
|
}).describe("Archived program.").optional()
|
|
2534
2534
|
});
|
|
2535
|
-
var BulkUpdateProgramsRequest = z.object({
|
|
2535
|
+
var BulkUpdateProgramsRequest = /* @__PURE__ */ z.object({
|
|
2536
2536
|
programs: z.array(
|
|
2537
2537
|
z.object({
|
|
2538
2538
|
program: z.object({
|
|
@@ -2608,7 +2608,7 @@ var BulkUpdateProgramsRequest = z.object({
|
|
|
2608
2608
|
tags: z.array(
|
|
2609
2609
|
z.object({
|
|
2610
2610
|
type: z.string().describe(
|
|
2611
|
-
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link
|
|
2611
|
+
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
|
|
2612
2612
|
).optional(),
|
|
2613
2613
|
props: z.record(z.string(), z.any()).describe(
|
|
2614
2614
|
'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
|
|
@@ -2620,7 +2620,7 @@ var BulkUpdateProgramsRequest = z.object({
|
|
|
2620
2620
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
2621
2621
|
).optional(),
|
|
2622
2622
|
custom: z.boolean().describe(
|
|
2623
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
2623
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
2624
2624
|
).optional(),
|
|
2625
2625
|
disabled: z.boolean().describe(
|
|
2626
2626
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -2720,7 +2720,7 @@ var BulkUpdateProgramsRequest = z.object({
|
|
|
2720
2720
|
returnEntity: z.boolean().describe("Whether to return updated programs in the response.").optional()
|
|
2721
2721
|
}).optional()
|
|
2722
2722
|
});
|
|
2723
|
-
var BulkUpdateProgramsResponse = z.object({
|
|
2723
|
+
var BulkUpdateProgramsResponse = /* @__PURE__ */ z.object({
|
|
2724
2724
|
results: z.array(
|
|
2725
2725
|
z.object({
|
|
2726
2726
|
itemMetadata: z.object({
|
|
@@ -2812,7 +2812,7 @@ var BulkUpdateProgramsResponse = z.object({
|
|
|
2812
2812
|
tags: z.array(
|
|
2813
2813
|
z.object({
|
|
2814
2814
|
type: z.string().describe(
|
|
2815
|
-
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link
|
|
2815
|
+
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
|
|
2816
2816
|
).optional(),
|
|
2817
2817
|
props: z.record(z.string(), z.any()).describe(
|
|
2818
2818
|
'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
|
|
@@ -2824,7 +2824,7 @@ var BulkUpdateProgramsResponse = z.object({
|
|
|
2824
2824
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
2825
2825
|
).optional(),
|
|
2826
2826
|
custom: z.boolean().describe(
|
|
2827
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
2827
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
2828
2828
|
).optional(),
|
|
2829
2829
|
disabled: z.boolean().describe(
|
|
2830
2830
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|
|
@@ -2929,16 +2929,16 @@ var BulkUpdateProgramsResponse = z.object({
|
|
|
2929
2929
|
).optional()
|
|
2930
2930
|
}).describe("Summary metadata for the bulk update.").optional()
|
|
2931
2931
|
});
|
|
2932
|
-
var CountProgramsRequest = z.object({
|
|
2932
|
+
var CountProgramsRequest = /* @__PURE__ */ z.object({
|
|
2933
2933
|
options: z.object({
|
|
2934
2934
|
filter: z.record(z.string(), z.any()).describe("WQL filter for the programs to count.").optional().nullable()
|
|
2935
2935
|
}).optional()
|
|
2936
2936
|
});
|
|
2937
|
-
var CountProgramsResponse = z.object({
|
|
2937
|
+
var CountProgramsResponse = /* @__PURE__ */ z.object({
|
|
2938
2938
|
count: z.number().int().describe("Number of programs matching the filter and caller visibility.").optional()
|
|
2939
2939
|
});
|
|
2940
|
-
var ListSampleProgramsRequest = z.object({});
|
|
2941
|
-
var ListSampleProgramsResponse = z.object({
|
|
2940
|
+
var ListSampleProgramsRequest = /* @__PURE__ */ z.object({});
|
|
2941
|
+
var ListSampleProgramsResponse = /* @__PURE__ */ z.object({
|
|
2942
2942
|
programs: z.array(
|
|
2943
2943
|
z.object({
|
|
2944
2944
|
program: z.object({
|
|
@@ -3014,7 +3014,7 @@ var ListSampleProgramsResponse = z.object({
|
|
|
3014
3014
|
tags: z.array(
|
|
3015
3015
|
z.object({
|
|
3016
3016
|
type: z.string().describe(
|
|
3017
|
-
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link
|
|
3017
|
+
"SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns."
|
|
3018
3018
|
).optional(),
|
|
3019
3019
|
props: z.record(z.string(), z.any()).describe(
|
|
3020
3020
|
'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
|
|
@@ -3026,7 +3026,7 @@ var ListSampleProgramsResponse = z.object({
|
|
|
3026
3026
|
"SEO tag inner content. For example, `<title> inner content </title>`."
|
|
3027
3027
|
).optional(),
|
|
3028
3028
|
custom: z.boolean().describe(
|
|
3029
|
-
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
3029
|
+
"Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
|
|
3030
3030
|
).optional(),
|
|
3031
3031
|
disabled: z.boolean().describe(
|
|
3032
3032
|
"Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
|