---
title: "Plan Custom Template"
method: POST
path: "/brand-kit/layout-templates/custom/plan"
tags: ["Brand Kit"]
---

# Plan Custom Template

`POST /brand-kit/layout-templates/custom/plan`

## Request

- Base URL: `https://be.graph8.com/api/v1`
- URL: `https://be.graph8.com/api/v1/brand-kit/layout-templates/custom/plan`
- Auth: HTTP bearer

Preview the section plan for an idea. Builds nothing, stores nothing.

The review step: it returns the plan a build WOULD follow, so the plan can
be edited and handed back to `POST /layout-templates/custom` instead of
discovering the interpretation was wrong after the page exists.

## Headers

- `Authorization` string, nullable
- `X-Target-Org-Id` string, nullable

## Request body

- CustomTemplatePlanRequest: Mirrors `campaign_builder.routers.brand_kit.CustomPlanRequest`. The preview half of the pair above. Builds nothing and stores nothing.
  - `idea` string, required: Plain-language description of the page to plan.
  - `name` string, nullable: Short title.
  - `attached_assets` AttachedAsset[]: Images and videos the plan must place.
    - `type` 'image' | 'video', required: Asset kind.
    - `id` string, required: Asset id.
    - `url` string, required: Public URL the generated page will reference.
    - `poster_url` string, nullable: Poster frame for a video.
    - `alt_text` string, nullable: Alt text.
    - `title` string, nullable: Title.
    - `position_hint` 'hero' | 'body' | 'any': Where the asset should land on the page.

## Response `200`

Successful Response

- ApiResponseStudioPayload
  - `data` StudioPayload, required: An open envelope for one settings block, document or brand artefact. OPEN on purpose. These surfaces are configuration and generated content, and both grow: a new toggle on a settings block or a new field on a generated document must reach a caller on the day it ships, not on the day somebody remembers to widen a mirror. A closed response model here would silently DROP the new key, which reads to the caller as "the product does not have that setting". The request side is the opposite and is mirrored exactly - see the module docstring for why the asymmetry is deliberate.
  - `pagination` PaginationMeta
    - `page` integer, required: Current page number (1-indexed)
    - `limit` integer, required: Items per page
    - `total` integer, required: Total number of items
    - `has_next` boolean, required: Whether there are more pages
    - `next_cursor` string, nullable: Opaque cursor for the next page; null when there are no more items. Pass it back as the `cursor` query param to fetch the following page without computing page numbers.
    - `total_available` integer, nullable: Search endpoints only: how many records really match, when known. Can be larger than `total`, which is capped at the 10,000 results that can be paged. For company search this is a distinct-company estimate. Null when unknown; absent outside search.
    - `total_is_lower_bound` boolean, nullable: Search endpoints only: true when more records match than `total` shows (the result set is larger than the 10,000 results that can be paged). Absent outside search.
    - `notes` string[], nullable: Search endpoints only: plain-language notes about the result, e.g. that more records match than can be paged, or that a reversed `between` range was put in order.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/graph8/apis/graph8-developer-api.md) · [All operations](https://skmtc.dev/graph8/apis/graph8-developer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/graph8/apis/graph8-developer-api/revisions/2e7cfa0ca921?raw)