Skip to main content
A Page is a published landing page composed of an ordered list of typed blocks — headings, text, images, buttons, forms. The v1 API surface is read-only: list pages, read a single page with its full block tree. Authoring stays in the dashboard editor.
v1 Pages is read-only. There is no POST, PATCH, or DELETE for pages or blocks via the API. To create or edit a page, use the dashboard. To collect submissions, see Submissions.

The two endpoints

Read a page

Response (truncated):
See the full field reference on the Page object and the per-block-type config reference on Blocks.

The block tree

Blocks are returned as a flat ordered array. Render them in the order given by sort_order (which is also the array order). Each block has:
The config field’s shape depends on type. The wire schema types it as unknown because there are 26+ block variants, each with its own discriminated config shape. See Blocks for the per-type reference.

Block categories

Blocks fall into three categories: A page is considered a form page as soon as it contains any form_* block. The form_submit block is the trigger that ships submissions to Awardee.

Status

Pages have a published-state status field: GET /pages returns all four statuses — filter client-side if you only want published pages.

Submissions are separate

Form fills land in a separate resource. The page tells you what blocks exist; submissions tell you what visitors filled in. See Submissions.

Page object

Field-by-field reference for the page-level response.

Blocks

Per-block-type config reference. JSON shapes for every block in the registry.