Create a page.

POST /v1/pages

scope: pages:writeCreator & Pro plansquota cost: 1send an Idempotency-Key

Create a new bio page as an UNPUBLISHED draft — the same path as the dashboard's New page dialog (slug derived from the title and deduped). Nothing goes live until Publish page.

Requires scope: pages:write. Plan entitlement: public_api (Creator and Pro).

Consequential operation — send an Idempotency-Key header.

Open in Claude ↗Open in ChatGPT ↗

Try it

Request.

curl "https://app.getbioflow.com/v1/pages" \
  -X POST \
  -H "Authorization: Bearer bf_live_YOUR_KEY" \
  -H "Idempotency-Key: a-unique-id-per-attempt" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "string",
    "theme_preset_key": "string",
    "header_layout": "classic"
  }'

Request body

JSON body (application/json).

Request-body fields for createPage
Field	Type	Required	Description
`title`	string	yes	—
`theme_preset_key`	string	no	One of the 13 canonical theme preset keys
`header_layout`	classic \| banner \| hero \| cutout	no	—

Response

201 — The created page.

Fields of the 201 response for createPage
Field	Type	Description
`id`	string	—
`title`	string	—
`description`	string	—
`slug`	string	—
`status`	DRAFT \| PUBLISHED \| ARCHIVED	—
`locale`	string	—
`public_url`	string \| null	Live URL when routed; null for unrouted drafts
`theme`	object	—
`draft`	object	—
`published`	object	—

Every response also carries X-Request-Id plus the IETF draft-11 RateLimit / RateLimit-Policy headers.

Errors

What can go wrong here.

Problem codes this operation can return
Code	Status	Meaning
`invalid_request`	400	The request body or parameters failed validation
`invalid_api_key`	401	Missing, malformed, unknown, disabled, or expired API key
`insufficient_scope`	403	The API key was not granted the required scope
`feature_not_enabled`	403	The workspace plan does not include public API access
`test_key_read_only`	403	Test-mode keys are restricted to read operations
`rate_limited`	429	Per-key rate limit exceeded
`quota_exhausted`	429	Monthly API quota exhausted
`internal_error`	500	Something went wrong on our side

All errors are RFC 9457 application/problem+json — branch on code, quote request_id to support. Full registry on the API docs hub; interactive playground in the API reference.