> Production API availability: use /api/v1/help?view=guides and the resource operations catalog before following a recipe. Some localhost capabilities are not deployed yet; an absent operation is unavailable.
Pick a small outcome
Start with a heading, a paragraph and an existing call to action. One section is enough to learn the workflow without changing the whole page.
Inspect the page mapping
Fetch the board and locate the target page in its list. Read the section's template, CSS configuration, data mapping and mapped menu or module record.
curl --fail-with-body "$API_URL/databoards/$BOARD_ID/page-flow" \
-H "Authorization: Bearer $API_KEY"Some sections retain fallback content as well as a mapping. When a mapping is active, its source is authoritative. Changing fallback text alone may have no visible effect.
Prepare the patch
Read GET /api/v1/databoards/{id}/agent-context using your scoped key. Prepare only the intended source edits, then POST the JSON envelope to /api/v1/databoards/{id}/patch/dry-run. Review the result before posting it to /api/v1/databoards/{id}/patch. Retain the original board response for recovery.
Keep the section native
Use header, body and footer fields. Reuse the site typography and spacing. If a diagram is needed, upload it through the asset API and use the resulting asset URL in the mapped image field.
Do not put a new stylesheet or JavaScript application inside a paragraph field. A new reusable behavior belongs in the shared template and Sass v2 component system.
Review the result
After the approved patch is applied, generate the intended preview target. Check the heading, body, CTA destination and mobile wrapping. Open the destination: a correctly styled link can still point to the wrong page.
Continue with a complete patch
See agent patches for the JSON envelope, intent fields, HTTP validation and apply requests. See data mapping to inspect source and target paths in the UI.