POST
Create a store FAQ entry

Authorizations

Authorization
string
header
required

A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.

Headers

Idempotency-Key
string
required

A unique key per logical write. Replaying a request with the same key returns the first response byte for byte instead of applying the write twice.

Body

application/json

Appended to the end of the store's list. is_published defaults to false when omitted, the same draft-first posture the dashboard's own create form takes: a plain bool needs no explicit-empty distinction here the way a clearing PUT does, because false is already an unambiguous, ordinary answer.

question
string
required

1 to 300 characters after trimming. The accordion heading.

answer
string
required

1 to 5000 characters after trimming. Plain text, never HTML.

is_published
boolean

Whether the storefront serves this entry, and whether it is marked up as FAQPage structured data. Defaults to false.

Response

Created

data
object