pub.chive.moderation.createReport

Report content for moderation review. Requires authentication. Duplicate reports from the same user for the same content are idempotent.

Repository @lexicons.governance.chive.pub did:plc:egjghlwgts2hlcer2txilxeh not from the namespace authority
Details · procedure
Kindprocedure
Authoritymoderation.chive.pub
Indexed

Procedure

procedure · POST

Input

application/json

Optional additional details about the report

  • maxLength: 2000

reason

requiredstring

Reason for reporting

  • knownValues: spam | inappropriate | copyright | misinformation | other

targetCollection

requiredstring

Collection NSID of the target content

targetUri

requiredstring · at-uri

AT-URI of the content to report

Output

application/json

id

requiredinteger

Report ID

success

requiredboolean

Whether the report was created

Errors

AuthenticationRequired

No description in schema.

InvalidRequest

No description in schema.

Similar lexicons

semantic match

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

  • Submit a moderation report regarding an atproto account or record. Implemented by moderation services (with PDS proxying), and requires auth.

  • Reports an account, a repository, or what someone wrote about one, to the moderation service, as the account logged in to this appview's pages.

  • File a moderation report against an account, a record, a hashtag, or a DM message.

  • Creates a private Community-moderator report for a linked post. Requires authenticated service authorization.

  • Submit a user-initiated report on a post, reply, or actor account. The reporter DID is read from the authenticated principal. Reports are dedupe-forever on (reporter, subject): a duplicate submission returns the existing report id with `deduped: true` and no new row is inserted. Per-reporter rate limit applies (5/hour, 50/day). Reports are server-side records only — they are NEVER published as PDS records, never broadcast on the firehose, and are only readable by moderators via the admin surface