POST
Reorder the store's FAQ list

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

REPLACES THE WHOLE ORDER, not a moved id and a target index: send every one of this store's current entry ids exactly once, in the order they should appear. A duplicate, an id from another store, or a list missing an entry someone else just added is refused wholesale as invalid_reorder rather than applying a partial order nobody chose.

ordered_ids
string[]
required

Response

Success

data
object[]
page
object