place.stream.beta.getStatus

Report an account's access status for a named beta feature: whether it has been granted (via a trusted place.stream.beta.invite, or because this node isn't beta-gating the feature), has an outstanding place.stream.beta.request, or neither. Defaults to the authenticated caller when `did` is omitted.

Repository @stream.place did:plc:rbvrr34edl5ddpuwcubjiost not from the namespace authority
Details · query
Kindquery
Authoritybeta.stream.place
Indexed

Query

query · GET

Parameters

query string

did

string · did

Account to check. Defaults to the authenticated caller's DID when omitted.

feature

requiredstring

Identifier of the beta feature to check (e.g. "vod").

Output

application/json

did

requiredstring · did

The account this status applies to.

feature

requiredstring

The feature this status applies to (echoes the request).

status

requiredstring

granted: the account may use the feature. requested: no grant yet, but an access request is on file. none: no grant and no request.

  • knownValues: granted | requested | none

Errors

DidRequired

No did supplied and the request was not authenticated, so there is no account to check.

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • place.stream.beta.request

    record not from the namespace authority

    Requests access to a named beta feature on this network. Published in the requester's own repo, so the requesting account is the record's authority — there is no separate subject field. Operators index these to surface who is waiting for access; granting access is a separate place.stream.beta.invite record issued by the operator-trusted issuer. Each (requester, feature) pair gets its own record.

  • place.stream.beta.invite

    record not from the namespace authority

    Grants a single account access to a named beta feature on this network. Records live in a project-operated repo (the streamplace node's `--beta-invite-did`); operators trust invites only from that one account, by configuration. Each (did, feature) pair gets its own record so individual features can be revoked independently by deleting the corresponding record.

  • Current verification status of an account as known to the AppView.