@picked/client 0.0.1-dev.1786072899095 → 0.0.1-dev.1786601464574

package/dist/docs/reference/dashboard/content/blocks.mdx

@@ -0,0 +1,57 @@
+---
+type: reference
+layout: docs
+---
+
+import { Screenshot } from '../../../../../components/Screenshot'
+
+# Blocks
+
+A Block is a reusable schema fragment that you embed inside a Model, so that a common structure is defined one time.
+
+<Screenshot
+  route="/{orgSlug}/{projectId}/workspaces/{workspaceId}/blocks"
+  alt="The blocks list in the schema builder on the Picked dashboard"
+/>
+
+## What a Block is
+
+A Block is a schema fragment with its own **Key**. A
+[Model](/reference/dashboard/content/models) gives its shape to a whole Page or Step. A
+Block is a part that you put into one or more Models. Define the shape one time, then
+reuse it everywhere.
+
+A Block holds no data of its own. The content that fills a Block sits inside the entry
+of the Model that embeds it.
+
+## Where a Block appears
+
+**CMS** in the sidebar holds **Blocks**, and that list shows every Block in the
+workspace. **Pages** holds **Page Sections**, which is the same list limited to the
+Section category.
+
+## Category
+
+| Category | What it does |
+| --- | --- |
+| **Section** | Marks the Block as a page section. A **Page Sections** field accepts it. |
+| **None (general content)** | Gives the Block no layout role. |
+
+The category is fixed when you create the Block. You cannot change it later.
+
+A **Content block** field holds the category of the Blocks that it accepts. Give that
+field the **Section** category to build a page section list.
+
+A field set to **Any category** accepts every Block in the workspace. This is the only
+kind of field that can hold a Block with no category.
+
+## Field types
+
+A Block holds the same field types as a Model. See
+[Field types](/reference/dashboard/content/models#field-types).
+
+## Related
+
+- [About the content model](/explanation/the-content-model) — why Blocks exist.
+- [How to reuse a section](/how-to/reuse-a-section)
+- [Models](/reference/dashboard/content/models)

package/dist/docs/reference/dashboard/content/content-entries.mdx

@@ -7,7 +7,7 @@ import { Screenshot } from '../../../../../components/Screenshot'
 
 # Content Entries
 
-A Content Entry is an instance of a layout filled with real data. A Page renders one entry; a Flow Step can render one too.
+A content entry is one instance of a Model, filled with real data. A Page renders one entry, and a Flow Step can render one too.
 
 <Screenshot
   route="/{orgSlug}/{projectId}/workspaces/{workspaceId}/content"
@@ -16,29 +16,80 @@ A Content Entry is an instance of a layout filled with real data. A Page renders
 
 ## What a content entry is
 
-A Content Entry is an instance of a layout's schema. The [layout](/reference/dashboard/content/layouts) defines the fields; the entry holds the actual values. One layout can back many entries, each with its own data.
+A content entry is an instance of the schema of a
+[Model](/reference/dashboard/content/models). The Model sets the fields, and the entry
+holds the values. One Model backs many entries, and each entry holds its own data.
+
+The Model of an entry is fixed when you create the entry.
+
+## The entries list
+
+**CMS** in the sidebar holds **Content entries**, with a count of every entry in the
+workspace.
+
+| Column | What it shows |
+| --- | --- |
+| Title | The value of the first single-line text field of the entry. It falls back to the entry id when no such field holds a value. |
+| Model | The Model that the entry belongs to. |
+| Entry ID | The stable id of the entry. |
+| Last updated | When somebody last saved the entry. |
+
+The **Model** filter narrows the list to one Model. The list has no search, because the
+title is derived at read time and is not a column that Picked can search.
 
 ## How entries bind to pages and steps
 
-A [Page](/reference/dashboard/content/pages) has a single Step, and that Step links to its entry through the layout content link. A Flow [Step](/reference/dashboard/steps) backed by a Step Layout binds an entry the same way. When the SDK renders the Page or Step, it resolves the linked entry and hands its data to your component.
+A [Page](/reference/dashboard/content/pages) has a single Step, and that Step links to
+its entry through the layout content link. A Flow [Step](/reference/dashboard/steps)
+with a Step Layout binds an entry the same way. When the SDK renders the Page or the
+Step, it resolves the linked entry and gives the data to your component.
 
 ## Edit entry data
 
-The entry editor renders a form from the layout schema. There is one input for each
-field, in the order that the schema sets. A repeatable field appears as a sortable
+The entry editor renders a form from the schema of the Model. There is one input for
+each field, in the order that the schema sets. A repeatable field shows as a sortable
 list. You can add to that list and put it into a new order. A group field holds its
 inputs under one heading.
 
+## Reference fields
+
+A [Reference field](/reference/dashboard/content/models#reference-fields) holds a pointer
+at another entry, and not a copy of it.
+
+| Control | What it does |
+| --- | --- |
+| **Choose entry** | Opens the entry picker. |
+| **Change entry** | Opens the entry picker on a field that holds a target already. |
+| **Clear** | Removes the pointer. It does not delete the entry. |
+
+The entry picker lists the entries that the **Target Model** of the field allows, and it
+has a search box. **Open model** opens the Model of an entry in a new tab.
+
 ## Validation
 
-Invalid data appears as an error on each field. The error carries a path in the JSON
-style, and it points at the exact place in the entry, for example
-`sections[0].data.title`. Fix every error before you publish, because Picked serves
+Invalid data shows as an error on each field. The error carries a path in the JSON style,
+and it points at the exact place in the entry, for example `sections[0].data.title`.
+
+A reference field reports an error when its target does not exist, or when the target
+belongs to the wrong Model. Fix every error before you publish, because Picked serves
 valid content only.
 
+## Delete rules
+
+Picked does not delete an entry while something still points at it.
+
+| Condition | Result |
+| --- | --- |
+| A Step uses the entry as its layout | The delete stops. |
+| Another entry points at it through a Reference field | The delete stops. |
+
+Clear the reference on the other entry first, then delete the target.
+
 ## Related
 
 - [About the content model](/explanation/the-content-model) — why the schema and the data
   are separate.
-- [How to fill and publish a page](/how-to/fill-and-publish-a-page)
-- [Page and step layouts](/reference/dashboard/content/layouts)
+- [About content references](/explanation/content-references) — why a delete stops.
+- [How to create a content entry](/how-to/create-a-content-entry)
+- [How to point one entry at another](/how-to/point-one-entry-at-another)
+- [Models](/reference/dashboard/content/models)

package/dist/docs/reference/dashboard/content/models.mdx

@@ -0,0 +1,108 @@
+---
+type: reference
+layout: docs
+---
+
+import { Screenshot } from '../../../../../components/Screenshot'
+
+# Models
+
+A Model is a reusable schema. It sets which fields a piece of content can hold, and it holds no data itself.
+
+<Screenshot
+  route="/{orgSlug}/{projectId}/workspaces/{workspaceId}/models"
+  alt="The models list in the schema builder on the Picked dashboard"
+/>
+
+## Where a Model appears
+
+**CMS** in the sidebar holds **Models**, and that list shows every Model in the
+workspace. The list shows the **Key** below the name, because the key is the value that
+a schema holds.
+
+Two shortcuts open a filtered subset of the same list. **Flows** holds **Step Layouts**,
+and **Pages** holds **Page Layouts**.
+
+## Category
+
+A category gives a Model a role. It decides where the Model appears, and what renders an
+entry that comes from it.
+
+| Category | It gives its shape to | What renders it |
+| --- | --- | --- |
+| **Page layout** | A standalone [Page](/reference/dashboard/content/pages). | The SDK renders the entry on your server. |
+| **Step layout** | One [Step](/reference/dashboard/steps) inside a Flow. | The Step renders the entry in the browser. |
+| **None (general content)** | Content with no layout role. | Nothing renders it directly. A [reference field](#reference-fields) reaches it. |
+
+A Model with no category holds content that other content points at, such as a product
+or a category. It appears under **CMS** only.
+
+:::warning
+The category is fixed when you create the Model. You cannot change it later.
+:::
+
+## Field types
+
+A Model is built from fields. Each field has a type. The type decides the editor for the
+field, and the shape of the value that the field holds.
+
+| Type | Holds | Use it for |
+| --- | --- | --- |
+| **Single line text** | A short string. | A title, a label, or a short headline. |
+| **Multi-line text** | A longer plain string. | A description, or a paragraph with no format marks. |
+| **Markdown** | A Markdown string. | Body copy with format marks. |
+| **Slug** | A URL-safe string. | A part of a path, or an identifier. |
+| **Number** | A numeric value. | A price, a count, or a rating. |
+| **Boolean** | A true or false value. | A toggle or a flag. |
+| **Date** | A date value. | A publish date or a deadline. |
+| **Color** | A color value. | A theme accent or a swatch. |
+| **JSON** | Any JSON value. | Structured data with no editor of its own. |
+| **Group** | An object of fields inside the Model. | A set of related fields, held together. |
+| **Content block** | A [Block](/reference/dashboard/content/blocks) schema inside the Model. | A shared schema fragment that you reuse. |
+| **Page Sections** | A repeatable Content block field, limited to the Section category. | The section list of a page. |
+| **Reference** | A pointer at another [content entry](/reference/dashboard/content/content-entries). | A product that points at its category. |
+| **Asset** | A link to an [Asset Library](/reference/dashboard/content/asset-library) item. | An image, a video, or a document. |
+| **HTML** | A link to a `.html` file in your library. | HTML that you wrote before, held inside the content. |
+
+## Reference fields
+
+A **Reference** field points at another content entry. The entry that you point at keeps
+its own data, and many fields can point at the same entry.
+
+| Option | Values | What it does |
+| --- | --- | --- |
+| **Target Model** | A Model, or **Any Model** | Limits which entries an editor can choose. |
+| **Repeatable** | On or off | On gives an ordered list of entries. Off gives one entry. |
+
+**Target Model** holds the `key` of the Model, and not its id. A duplicate of the
+workspace therefore keeps the constraint.
+
+A reference stays inside one workspace. A field cannot point at an entry in another
+workspace, and Picked reports such a target as unknown.
+
+## Repeatable and grouped fields
+
+You can make any field **repeatable**. It then shows as a sortable list of values, and
+not as one value. Use it for a gallery, for a list of features, or for any collection.
+
+A **Group** field holds a set of fields under one key, and it gives a structured object.
+Make a group repeatable to describe a list of objects, such as a list of feature cards.
+
+## Delete rules
+
+Picked does not delete a Model while something still needs it.
+
+| Condition | Result |
+| --- | --- |
+| Content entries still belong to the Model | The delete stops. |
+| A Reference field still holds the Model as its **Target Model** | The delete stops. |
+
+## Related
+
+- [About the content model](/explanation/the-content-model) — why a schema change does not
+  migrate your data.
+- [About content references](/explanation/content-references) — why a reference is a pointer.
+- [How to define a page layout](/how-to/define-a-page-layout)
+- [How to create a content entry](/how-to/create-a-content-entry)
+- [How to point one entry at another](/how-to/point-one-entry-at-another)
+- [Blocks](/reference/dashboard/content/blocks)

package/dist/docs/reference/dashboard/content/pages.mdx

@@ -24,12 +24,13 @@ choose, and the preview panel shows the page while it fills in.
 ## Change or remove the layout
 
 Use the change-layout control on the **Settings** tab to move the page to another
-Page Layout. When you unlink a layout, Picked separates the Content Entry from the
-page. It deletes no entry, but the page then has no content to render until you
-attach a layout again.
+[Page Layout](/reference/dashboard/content/models#category). When you unlink a layout,
+Picked separates the content entry from the page. It deletes no entry, but the page then
+has no content to render until you attach a layout again.
 
 ## Related
 
 - [About pages and flows](/explanation/pages-and-flows) — when to choose a Page.
 - [How to fill and publish a page](/how-to/fill-and-publish-a-page)
 - [How to server-render a page](/how-to/server-render-a-page)
+- [Models](/reference/dashboard/content/models) — the schema behind a Page.

package/dist/docs/reference/dashboard/fields.mdx

@@ -12,7 +12,7 @@ information such as a name, an email address, a preference, or a choice.
 
 This page covers the experience field, which collects visitor input. An experience
 field is not the same as a content field. A content field is part of the schema of a
-CMS layout. See [Page and Step Layouts](/reference/dashboard/content/layouts) for those.
+CMS layout. See [Models](/reference/dashboard/content/models) for those.
 
 <Screenshot
   route="/{orgSlug}/{projectId}/workspaces/{workspaceId}/fields"

package/dist/docs/reference/dashboard/steps.mdx

@@ -26,7 +26,7 @@ visitors do not see it.
 are `card`, `modal`, and `fullscreen`.
 
 A step can also carry a **Step Layout**. A step layout is a reusable CMS schema, and
-it gives the step a Content Entry. See [Page and Step Layouts](/reference/dashboard/content/layouts).
+it gives the step a Content Entry. See [Models](/reference/dashboard/content/models).
 
 ## Related
 
@@ -34,4 +34,4 @@ it gives the step a Content Entry. See [Page and Step Layouts](/reference/dashbo
 
 - [How to build a flow](/how-to/build-a-flow) — add a step and assign fields to it.
 - [How to reuse a step, a field, or an action](/how-to/reuse-a-step-field-or-action)
-- [Page and step layouts](/reference/dashboard/content/layouts) — the step layout schema.
+- [Models](/reference/dashboard/content/models) — the step layout schema.

package/dist/docs/reference/delivery-api/experience-content.md

@@ -5,7 +5,7 @@ layout: docs
 
 # Experience Content Endpoint
 
-Fetch the Content Entries that back a single experience's steps.
+Fetch the content entries that back the steps of a single experience.
 
 ## Request
 
@@ -29,7 +29,17 @@ GET /api/v1/projects/:projectId/experiences/:id/content
     {
       "id": "entry_789",
       "contentModelKey": "page-hero",
-      "data": { "title": "Spring sale", "body": "..." }
+      "data": {
+        "title": "Spring sale",
+        "category": { "contentEntryId": "entry_42", "contentModelKey": "category" }
+      }
+    }
+  ],
+  "references": [
+    {
+      "id": "entry_42",
+      "contentModelKey": "category",
+      "data": { "name": "Outerwear" }
     }
   ]
 }
@@ -39,14 +49,59 @@ GET /api/v1/projects/:projectId/experiences/:id/content
 | --- | --- | --- |
 | `experienceId` | `string` | The experience the content belongs to. |
 | `versionId` | `string \| null` | The published version id, or `null` on preview. |
-| `content[].id` | `string` | The Content Entry id. |
-| `content[].contentModelKey` | `string \| null` | The layout's Key, or `null` when it cannot be resolved. |
-| `content[].data` | `object` | The entry data. It matches the layout schema. |
+| `content[]` | `array` | The entries that the steps of the experience point at. |
+| `content[].id` | `string` | The content entry id. |
+| `content[].contentModelKey` | `string \| null` | The Key of the Model, or `null` when it cannot be resolved. |
+| `content[].data` | `object` | The entry data. It matches the schema of the Model. |
+| `references[]` | `array` | Every entry that a `reference` field reaches, in the same blob shape as `content[]`. |
+
+The published response and the preview response hold the same fields, and the same
+values, for the same content.
+
+## A reference field points at a separate blob
+
+A [Reference field](/reference/dashboard/content/models#reference-fields) arrives as a
+pointer, and not as the entry:
+
+```json
+{ "contentEntryId": "entry_42", "contentModelKey": "category" }
+```
+
+A repeatable Reference field arrives as an array of such pointers.
+
+The entry itself arrives in `references[]` under its own `id`. Look the pointer up
+there. The SDK does this for you, through
+[`useReference` and `getReference`](/reference/sdk/content).
+
+`references[]` holds each entry one time, for any number of fields that point at it. It
+omits the entries that are in `content[]` already.
+
+### What `references[]` omits
+
+Picked resolves a chain of references to a maximum depth of 5. It counts the depth from
+the entries in `content[]`. An entry is absent from `references[]` when Picked cannot
+resolve it:
+
+| Cause | Result |
+| --- | --- |
+| The target was deleted | The pointer stays. The entry is absent. |
+| The target is in another workspace | The pointer stays. The entry is absent. |
+| The chain makes a cycle | The pointer stays. The entry is absent. |
+| The chain is deeper than 5 | The pointer stays, with its `contentModelKey`. The entry is absent. |
+
+A pointer with no entry in `references[]` means that there is no such entry. Picked sends
+no empty blob for it.
+
+:::warning
+A reference pointer also carries a `data` field with the content of the target inlined.
+This is for the SDK versions that came before `references[]`. Read `references[]`
+instead. A later release removes the inline copy.
+:::
 
 ## An HTML asset comes back in the response
 
-A layout can have an [HTML asset](/reference/dashboard/content/asset-library) field. The value of that
-field arrives inside the response. The endpoint changes the reference to
+A Model can have an [HTML asset](/reference/dashboard/content/asset-library) field. The
+value of that field arrives inside the response. The endpoint changes the reference to
 `{ id, content }`. There, `content` holds the HTML that you uploaded, as a string. It
 is `null` when the endpoint cannot resolve it:
 
@@ -82,16 +137,16 @@ curl https://api.picked.app/api/v1/projects/proj_123/experiences/exp_123/content
   "versionId": "ver_456",
   "content": [
     { "id": "entry_789", "contentModelKey": "page-hero", "data": { "title": "Spring sale" } }
-  ]
+  ],
+  "references": []
 }
 ```
 
-See [Project Config](/reference/delivery-api/project-config) for the endpoint that links a step
-to an entry. See [Asset Library](/reference/dashboard/content/asset-library) for an HTML asset. See
-[Server Snapshot](/reference/sdk/ssr/serialize) for how the SDK reads this content.
-
 ## Related
 
 - [About the two APIs](/explanation/the-two-apis)
-- [Project config](/reference/delivery-api/project-config)
+- [About content references](/explanation/content-references) — why a reference is a pointer.
+- [Content](/reference/sdk/content) — how the SDK resolves a pointer.
+- [Project config](/reference/delivery-api/project-config) — the endpoint that links a step to an entry.
+- [Server Snapshot](/reference/sdk/ssr/serialize) — how the SDK reads this content.
 - [Preview, cache, and crawlers](/reference/delivery-api/preview-caching-crawling)

package/dist/docs/reference/delivery-api/workspace-schema.md

@@ -0,0 +1,74 @@
+---
+type: reference
+layout: docs
+---
+
+# Workspace Schema Endpoint
+
+A JSON Schema document for the structure of your project: content models, fields, feature keys, experience keys, and step keys. Tooling reads this endpoint to generate TypeScript types for your application.
+
+## Request
+
+```
+GET /api/v1/projects/:projectId/schema
+```
+
+| Parameter | In | Description |
+| --- | --- | --- |
+| `projectId` | path | The project whose schema to fetch. |
+| `preview_token` | query | Optional. Returns the preview (unpublished) schema when you send it. |
+
+## Response
+
+The response is a [JSON Schema draft 2020-12](https://json-schema.org/draft/2020-12/schema) document with Picked-specific extension fields:
+
+| Field | Description |
+| --- | --- |
+| `x-picked-schema-version` | Schema document version (currently `1`). |
+| `x-picked-source` | `"published"` or `"preview"` — mirrors the surface you requested. |
+| `x-picked-version-id` | Published workspace version id, or `null` on preview. |
+| `x-picked-step-content-models` | Map of step key → content model key, which gives each layout its type. |
+| `$defs.contentModels` | JSON Schema definitions for each content model. |
+| `$defs.contentBlocks` | JSON Schema definitions for reusable content blocks. |
+| `$defs.fields` | Object schema for project field values. |
+| `$defs.featureKeys` | String enum of feature keys. |
+| `$defs.experienceKeys` | String enum of experience keys. |
+| `$defs.stepKeys` | String enum of step keys. |
+
+## Published and preview
+
+On the published surface, the schema reflects your last published workspace. On the preview surface (`?preview_token=...`), the schema reflects the current draft workspace. See [Preview, cache, and crawlers](/reference/delivery-api/preview-caching-crawling).
+
+When no published schema exists, the published endpoint returns `404` and tells you to publish the workspace.
+
+## Example
+
+```bash
+curl https://api.picked.app/api/v1/projects/proj_123/schema
+```
+
+```json
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "picked:project/proj_123/schema",
+  "x-picked-schema-version": 1,
+  "x-picked-source": "published",
+  "x-picked-version-id": "ver_456",
+  "x-picked-step-content-models": {
+    "intro": "welcome-page"
+  },
+  "$defs": {
+    "contentModels": {},
+    "contentBlocks": {},
+    "fields": { "type": "object", "additionalProperties": false, "properties": {} },
+    "featureKeys": { "type": "string", "enum": ["default"] },
+    "experienceKeys": { "type": "string", "enum": ["welcome-survey"] },
+    "stepKeys": { "type": "string", "enum": ["intro"] }
+  }
+}
+```
+
+## Related
+
+- [Type generation](/reference/sdk/type-generation) — Generate TypeScript types from this schema in your app.
+- [Project Config](/reference/delivery-api/project-config) — Runtime project configuration for the SDK.

package/dist/docs/reference/glossary.md

@@ -74,14 +74,21 @@ documentation uses, and it names the others.
 
 | Term | What it is |
 | --- | --- |
-| **Page layout** | A reusable schema that sets which fields a Page can hold. The API type is `ContentModel`, and the dashboard list page is titled **Models**. |
-| **Step layout** | The same, for one Step inside a Flow. |
-| **Section** | A reusable schema fragment that you put inside one or more layouts. The API type is `ContentBlock`, and the dashboard list page is titled **Blocks**. |
-| **Content entry** | One instance of a layout, filled with real values. The dashboard list page is titled **Content**. |
+| **Model** | A reusable schema that sets which fields a piece of content can hold. The API type is `ContentModel`. The dashboard lists them under **CMS**, at **Models**. |
+| **Block** | A reusable schema fragment that you put inside one or more Models. The API type is `ContentBlock`. The dashboard lists them under **CMS**, at **Blocks**. |
+| **Content entry** | One instance of a Model, filled with real values. The dashboard lists them under **CMS**, at **Content entries**. |
+| **Category** | The role of a Model or a Block. It is fixed when you create the record. |
+| **Page layout** | A Model with the Page layout category. It sets which fields a Page can hold. |
+| **Step layout** | A Model with the Step layout category. It sets which fields one Step inside a Flow can hold. |
+| **Section** | A Block with the Section category. A **Page Sections** field accepts it. |
+| **General content** | A Model or a Block with no category. It has no layout role, and nothing renders its entries directly. |
+| **Reference** | A field that points one content entry at another. The pointer holds the id of the target, and not a copy of it. |
+| **Target Model** | The Model whose entries a Reference field accepts. It holds a Key. **Any Model** sets no limit. |
+| **Entry title** | The name that the entries list shows. It is the first single-line text field of the entry, and it falls back to the entry id. |
 | **Asset** | A file that your content points at: an image, a video, a document, or HTML. |
 | **Asset library** | The project-level store that holds your assets. |
 | **Design system** | A set of shared design decisions for a project. |
-| **Content schema** | The set of fields that a layout or a section defines. |
+| **Content schema** | The set of fields that a Model or a Block defines. |
 | **Asset version** | One file that somebody uploaded for an asset. The library keeps the earlier versions. |
 | **Validation error** | A report that one field in a content entry does not match its schema. It carries the path to the exact field. |
 
@@ -96,6 +103,7 @@ documentation uses, and it names the others.
 | **Slot** | A named mount point, rendered by `<ExperienceSlot name="…" />`. It maps to the `.picked-slot-<name>` selector. |
 | **Placement** | Where an experience renders against its target: `replace`, `before`, `prepend`, `append`, or `after`. |
 | **Target selector** | The selector that an experience renders into. |
+| **Content index** | The store of every content record that the client holds, keyed by id. `useContent(id)` and `useReference()` read it. |
 | **Snapshot** | The plain JSON that `serialize()` returns on your server, and that seeds the client in the browser. |
 | **Precondition** | A gate that decides whether Picked starts at all. |
 | **Visitor** | The person on your site. Picked gives each one a stable ID. A visitor is not a user. |

package/dist/docs/reference/management-api/error-handling.md

@@ -46,7 +46,7 @@ operation, or MFA. They match the `AuthErrorCode` enum in the schema.
 | Code | Description |
 |------|-------------|
 | `INVALID_CREDENTIALS` | The email address and the password do not match. |
-| `EMAIL_NOT_CONFIRMED` | The account is there, but nobody verified the email address. See [Authentication](/reference/management-api/authentication#verify-an-email-address). |
+| `EMAIL_NOT_CONFIRMED` | The account is there, but nobody verified the email address. See [Authentication](/reference/management-api/authentication#the-mutations). |
 | `USER_NOT_FOUND` | There is no account with that email address. |
 | `USER_ALREADY_EXISTS` | An account with that email address is there already. The API returns this when you create an account. |
 | `WEAK_PASSWORD` | The password is not strong enough. |
@@ -199,7 +199,7 @@ if (result.errors) {
 ### Refresh a token that expired
 
 A request can return `UNAUTHORIZED` while the caller holds a refresh token. Try a
-[session refresh](/reference/management-api/authentication#refresh-a-session) first. Do not treat it as a
+[session refresh](/reference/management-api/authentication#the-mutations) first. Do not treat it as a
 failure to sign in:
 
 ```javascript