Skip to main content

webiny-sdk

Using @webiny/sdk to read and write CMS data from external applications. Use this skill when the developer is building a Next.js, Vue, Node.js, or any external app that needs to fetch or write content to Webiny, set up the SDK, use the Result pattern, list/get/create/update/publish entries, filter and sort queries, use TypeScript generics for type safety, work with the File Manager, list languages, trigger or monitor background tasks, or create API keys programmatically. Covers read vs preview mode, the `values` wrapper requirement, correct method names, and the `fields` required parameter, and background task management via `sdk.tasks`. Also covers common SDK errors and troubleshooting — especially "Content model '<modelName>' not found" (which usually means the API key lacks permission, not that the model is missing) and the Website Builder starter pitfall of reusing NEXT_PUBLIC_WEBSITE_BUILDER_API_KEY for Headless CMS reads (that key has no CMS permissions by default and needs either extension or replaceme

Quellinformationen

Repository
webiny/webiny-js
Letzte Quellaktivität
24. Juli 2026 um 12:20
Erkannte Sprache von SKILL.md
Englisch
Sterne
8.045
Forks
682

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

SKILL.md wird angezeigt

SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau
name
webiny-sdk
description
Using @webiny/sdk to read and write CMS data from external applications. Use this skill when the developer is building a Next.js, Vue, Node.js, or any external app that needs to fetch or write content to Webiny, set up the SDK, use the Result pattern, list/get/create/update/publish entries, filter and sort queries, use TypeScript generics for type safety, work with the File Manager, list languages, trigger or monitor background tasks, or create API keys programmatically. Covers read vs preview mode, the `values` wrapper requirement, correct method names, and the `fields` required parameter, and background task management via `sdk.tasks`. Also covers common SDK errors and troubleshooting — especially "Content model '<modelName>' not found" (which usually means the API key lacks permission, not that the model is missing) and the Website Builder starter pitfall of reusing NEXT_PUBLIC_WEBSITE_BUILDER_API_KEY for Headless CMS reads (that key has no CMS permissions by default and needs either extension or replacement with a CMS-scoped key).
# Webiny SDK ## TL;DR The `@webiny/sdk` package provides a TypeScript interface for external apps (Next.js, Vue, Node.js) to interact with Webiny's Headless CMS and File Manager. Every method returns a `Result` object (checked with `isOk()`). Supports listing, getting, creating, updating, publishing, and unpublishing entries with filtering, sorting, pagination, and TypeScript generics for type safety. ## Installation & Setup ```bash npm install @webiny/sdk ``` Initialize once and reuse: ```typescript // lib/webiny.ts import { Webiny } from "@webiny/sdk"; export const webiny = new Webiny({ token: process.env.WEBINY_API_TOKEN!, endpoint: process.env.WEBINY_API_ENDPOINT!, tenant: process.env.WEBINY_API_TENANT || "root" }); ``` - `token` -- API key token generated in Webiny Admin (Settings > API Keys) - `endpoint` -- The base API URL, **without a trailing slash**. Run `yarn webiny info` in your Webiny project to find the API URL. For Website Builder projects use `NEXT_PUBLIC_WEBSITE_BUILDER_API_HOST`. - `tenant` -- Tenant ID, defaults to `"root"` > **IMPORTANT:** Never add a trailing slash to `endpoint`. The SDK appends `/graphql` to the endpoint internally, so `https://xxx.cloudfront.net/` will break all requests. ## The `fields` Parameter (Required) Every SDK method requires a `fields` array that specifies which fields to return. Omitting it will cause a runtime error. - Use `"values.<fieldId>"` for content fields: `"values.name"`, `"values.price"` - Use top-level field names for metadata: `"id"`, `"entryId"`, `"createdOn"`, `"status"` - Use dot notation for nested fields: `"values.author.name"` ```typescript // Minimal fields -- just IDs fields: ["id", "entryId"]; // Content fields fields: ["id", "entryId", "values.name", "values.price", "values.description"]; // Nested reference fields fields: ["id", "values.title", "values.author.name", "values.author.email"]; ``` ## CMS: Read vs Preview Mode `webiny.cms.listEntries` and `webiny.cms.getEntry` accept a `preview` parameter to control which revisions are returned: | `preview` | Returns | Use For | | ----------------- | ------------------------------------ | -------------------------------- | | `false` (default) | Published entries only | Public-facing apps, SSG | | `true` | Latest revision (draft or published) | Content preview, editorial tools | Write operations (`createEntry`, `updateEntryRevision`, etc.) are not affected by `preview`. ## The Result Pattern Every SDK method returns a `Result` object -- it never throws: ```typescript const result = await webiny.cms.listEntries({ modelId: "product", fields: ["id", "values.name"] }); if (result.isOk()) { console.log(result.value.data); // success -- typed data } else { console.error(result.error.message); // failure -- error info } ``` ## TypeScript Generics Pass a type parameter for full type safety on `values`: ```typescript import type { CmsEntryData } from "@webiny/sdk"; interface Product { name: string; price: number; sku: string; description: string; category?: CmsEntryData<ProductCategory>; } interface ProductCategory { name: string; slug: string; } const result = await webiny.cms.listEntries<Product>({ modelId: "product", fields: ["id", "entryId", "values.name", "values.price", "values.sku"] }); if (result.isOk()) { // result.value.data is CmsEntryData<Product>[] const products = result.value.data; // products[0].values.name -- fully typed } ``` Reference fields like `category` are typed as `CmsEntryData<T>`, which wraps referenced entries with `id`, `entryId`, and `values`. ## Reading Data ### List Entries ```typescript const result = await webiny.cms.listEntries<Product>({ modelId: "product", fields: ["id", "entryId", "values.name", "values.price"], sort: { "values.name": "asc" }, limit: 10 }); ``` ### List with Filters ```typescript const result = await webiny.cms.listEntries<Product>({ modelId: "product", fields: ["id", "entryId", "values.name", "values.price"], where: { "values.price_gte": 100, "values.name_contains": "Pro" }, sort: { "values.price": "desc" } }); ``` ### Filter Operators | Operator | Description | Example | | -------------- | ------------------ | -------------------------------------------- | | `_eq` | Equals (default) | `"values.status": "active"` | | `_not` | Not equals | `"values.status_not": "archived"` | | `_contains` | Contains substring | `"values.name_contains": "Pro"` | | `_startsWith` | Starts with | `"values.name_startsWith": "Web"` | | `_gt` / `_gte` | Greater than / >= | `"values.price_gte": 100` | | `_lt` / `_lte` | Less than / <= | `"values.price_lt": 500` | | `_in` | In array | `"values.status_in": ["active", "featured"]` | ### Sort Format Sort is a `Record<string, "asc" | "desc">` object: ```typescript sort: { "values.name": "asc" } // alphabetical sort: { "values.price": "desc" } // highest price first sort: { "values.createdOn": "desc" } // newest first ``` ### Get Single Entry Use `where` with either `id` (revision ID) or `entryId`: ```typescript // By revision ID const result = await webiny.cms.getEntry<Product>({ modelId: "product", where: { id: "abc123#0001" }, fields: ["id", "entryId", "values.name", "values.price"] }); // By entry ID (gets latest published revision) const result = await webiny.cms.getEntry<Product>({ modelId: "product", where: { entryId: "abc123" }, fields: ["id", "entryId", "values.name"] }); ``` ### Preview Mode (Drafts) Pass `preview: true` to `listEntries` or `getEntry` to access unpublished/draft content: ```typescript const result = await webiny.cms.listEntries<Product>({ modelId: "product", fields: ["id", "entryId", "values.name"], preview: true // returns drafts + published }); ``` ## Writing Data > **CRITICAL:** Content fields MUST be wrapped inside a `values` key in the `data` object. Passing fields directly (without `values`) will result in an empty or malformed entry. ### Create an Entry ```typescript const result = await webiny.cms.createEntry({ modelId: "contactSubmission", data: { values: { // ← REQUIRED: wrap all content fields in `values` name: "John Doe", email: "john@example.com", message: "Hello from the contact form!" } }, fields: ["id", "entryId"] }); ``` ### Update an Entry Revision The method is `updateEntryRevision`, not `updateEntry`. Use `revisionId` (the full `entryId#revisionNumber`, e.g. `"abc123#0001"`): ```typescript const result = await webiny.cms.updateEntryRevision({ modelId: "product", revisionId: "abc123#0001", // ← note: revisionId, not id data: { values: { // ← REQUIRED: wrap fields in `values` price: 29.99 } }, fields: ["id", "entryId", "values.price"] }); ``` ### Publish / Unpublish The methods are `publishEntryRevision` and `unpublishEntryRevision`, not `publishEntry`/`unpublishEntry`. Both require `revisionId` and `fields`: ```typescript await webiny.cms.publishEntryRevision({ modelId: "product", revisionId: "abc123#0001", fields: ["id", "entryId", "status"] }); await webiny.cms.unpublishEntryRevision({ modelId: "product", revisionId: "abc123#0001", fields: ["id", "entryId", "status"] }); ``` ### Delete an Entry Revision ```typescript await webiny.cms.deleteEntryRevision({ modelId: "product", revisionId: "abc123#0001", fields: [] }); ``` ## Languages `webiny.languages.listLanguages()` returns all **enabled** languages — disabled languages are always filtered out server-side, so no filter parameter is needed. ```typescript import type { Language } from "@webiny/sdk"; const result = await webiny.languages.listLanguages(); if (result.isOk()) { const languages: Language[] = result.value; // languages[0].code, .name, .direction, .isDefault } ``` The `Language` type: ```typescript interface Language { id: string; code: string; // e.g. "en-US" name: string; // e.g. "English (US)" direction?: "ltr" | "rtl"; isDefault?: boolean; } ``` ## File Manager ```typescript // List files const files = await webiny.fileManager.listFiles({ limit: 20, fields: ["id", "key", "name", "size", "type", "src"] }); // Upload a file (returns presigned URL for direct S3 upload) const uploaded = await webiny.fileManager.uploadFile({ file: myFile }); ``` ## Creating API Keys via Code For programmatic access, create API keys as an extension: ```typescript // extensions/MyApiKey.ts import { ApiKeyFactory } from "webiny/api/security"; class MyApiKeyImpl implements ApiKeyFactory.Interface { execute(): ApiKeyFactory.Return { return [ { name: "Universal API Key", slug: "universal-key", token: "wat_12345678", permissions: [{ name: "*" }] } ]; } } export default ApiKeyFactory.createImplementation({ implementation: MyApiKeyImpl, dependencies: [] }); ``` Register (**YOU MUST include the `.ts` file extension in the `src` prop** — omitting it will cause a build failure): ```tsx <Api.Extension src={"/extensions/MyApiKey.ts"} /> ``` ## Background Tasks `webiny.tasks` wraps the Background Tasks GraphQL API. All methods return a `Result` and never throw. ### List Task Definitions Returns all registered task definitions — use this to discover valid `definition` IDs before triggering.
Auf GitHub ansehen
Diese SKILL.md ist sehr gross, daher zeigt SkillsMP hier nur den ersten Abschnitt. Auf GitHub ansehen