support.supper.actor.listSupporting
List the creators a supporter has payment-verified support.supper.feed.post records for across all repos. The cross-repo inverse of feed.listSupporters. Self-authorship alone is not payment evidence. Public read; returns creator DIDs and aggregate counts only, never amounts, emails, or processor identifiers.
Details · query
| Kind | query |
|---|---|
| Authority | actor.supper.support |
| Indexed |
Query
query · GETParameters
query stringOutput
application/jsoncursor
stringmaxLength: 4096
#supportingView
objectProperties
Creator/project DID the supporter supports.
lastSupportedAt
string · datetimeMost recent indexed support event for this creator.
postCount
integerNumber of verified feed posts the supporter authored for this creator.
minimum: 0
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
List the distinct supporter DIDs for a creator across all repos, derived from verified support.supper.feed.post records pointing at the creator. Creator-owned support.supper.entitlement anchors identify unlockable surfaces but do not represent a supporter-to-creator edge. Public read; returns DIDs and aggregate counts only, never amounts, emails, processor identifiers, or private member data.
-
Get a creator's verified cross-repo support feed: support.supper.feed.post records authored on every supporter repo whose recipient is the named creator, newest first. Every returned post carries a payment strongRef verified against an active broker-attested payment; the AppView never re-derives amount/currency/status. Public read; unverified posts are never returned and outputs carry only public record bodies, never private metadata.
-
Get a paginated list of supporters for a subject.
-
Get a creator/supporter's cross-account Supper page: the indexed support.supper.actor.profile marker plus the actor.about section and all actor.project showcase entries for the account, regardless of which compatible app wrote them. Public Supper AppView read; responses contain only public record bodies and never private metadata or processor identifiers.
-
Public actors who cheered a canonical post, with one entry per actor. No authentication is required; responses contain public records only.