Skip to main content
POST
Preview backing an opinion (step 1 of 2)

Authorizations

Authorization
string
header
required

Personal API key issued per SeeSaw user account: Authorization: Bearer sspat_…. Manage keys on the app API (/v1/users/me/api-keys). Revocation propagates within ~60 seconds (validation cache window).

The key's scopes decide what it may do: every key has read; a key created with ["read","write"] may also use the six write operations (marked x-required-scope: write in this document). Scopes are fixed at creation — to gain write access, create a new key. A read-only key calling a write operation gets 403 FORBIDDEN_SCOPE.

Path Parameters

id
string<uuid>
required

Opinion UUID.

Body

application/json
topic_id
string<uuid>
required

The topic the opinion belongs to.

Response

The preview (check can_back before confirming)

can_back
boolean
required
summary
object
required

What the user confirms before POST /backs. max_relay_payback_sapphires is conditional: the most this seat can receive if two more backers follow. Nothing is paid if nobody follows.

reason
enum<string>

Present only when can_back is false.

Available options:
OPINION_INACTIVE,
ALREADY_BACKED,
TOPIC_CLOSED,
INSUFFICIENT_BALANCE,
OPINION_BACK_FULL
confirm_token
string
expires_at
string<date-time>