Skip to main content
The engagement endpoints let users interact with pods in three ways: commenting for discussion, voting to influence curation rewards, and submitting qualitative feedback alongside a vote. All engagement endpoints require Privy cookie authentication. Votes are on-chain actions on Base — you must submit the transaction first and pass the resulting hash to the API.

List comments for a pod


Returns all comments posted on a pod, ordered by creation time. Auth: Privy cookie

Path parameters

string
required
The internal ID of the pod.
Response 200

Response fields

array
required
Ordered list of comments on the pod.
string
required
Internal comment ID.
string
required
The comment text.
string (date-time)
required
ISO 8601 timestamp when the comment was posted.
string
required
Display name of the commenter.
string | null
Avatar URL for the commenter.

Example


Create a comment on a pod


Posts a new comment on a pod. Returns the internal ID of the created comment. Auth: Privy cookie

Path parameters

string
required
The internal ID of the pod.

Request body

string
required
The internal ID of the pod (must match the path parameter).
string
required
The comment text.
Response 201

Example


Register a vote for a pod


Records a vote for a pod after the corresponding on-chain transaction has been confirmed on Base. Votes affect the pod’s curation score for the given epoch and determine reward distribution.
You must submit the vote transaction on Base before calling this endpoint. Passing an invalid or unconfirmed txHash will result in a 400 error.
Auth: Privy cookie

Path parameters

string
required
The internal ID of the pod being voted on.

Request body

string
required
The internal ID of the pod (must match the path parameter).
integer
required
The epoch number in which this vote is being cast.
number
required
The weighted vote amount, derived from the voter’s veREPPO balance.
boolean
required
true for an up-vote, false for a down-vote.
string
required
Transaction hash of the on-chain vote submitted on Base.
Response 200

Response fields

string
required
Internal ID of the created vote record.

Example


Store vote feedback for a pod


Stores qualitative written feedback alongside a vote. Use this to capture the voter’s reasoning — the feedback is linked to the specific vote context (epoch, voting power, and direction). Auth: Privy cookie

Path parameters

string
required
The internal ID of the pod.

Request body

string
required
The internal ID of the pod.
string
required
The voter’s written rationale or qualitative assessment.
integer
required
The epoch number in which the vote was cast.
number
required
The voter’s veREPPO voting power at the time of the vote.
boolean
required
true if the associated vote was an up-vote, false for a down-vote.
string
required
Internal ID of the datanet the pod belongs to.
number
required
The weighted vote amount associated with this feedback entry.
Response 201

Example