# pet.trezy.getForgeries

> Published by [trezy.pet](https://lexicon.garden/identity/did:plc:ollch4g7tes2reb5eceiwuol)

✓ This is the authoritative definition for this NSID.

## Links

- [View on Lexicon Garden](https://lexicon.garden/lexicon/did:plc:ollch4g7tes2reb5eceiwuol/pet.trezy.getForgeries)
- [Documentation](https://lexicon.garden/lexicon/did:plc:ollch4g7tes2reb5eceiwuol/pet.trezy.getForgeries/docs)
- [Examples](https://lexicon.garden/lexicon/did:plc:ollch4g7tes2reb5eceiwuol/pet.trezy.getForgeries/examples)

## Definitions

### `pet.trezy.getForgeries`

**Type**: `query`

Every record of this account's that an ingest guard refused, one entry each, with the reason written out. Reads `trezy_pet_rejections`, which the guards fill as forged records arrive on the firehose — so this is a report of what was already stopped, not a check performed now. Nothing here changes what the account may do: the refusal happened at ingest and the ledger never saw the record.

#### Parameters

| Property | Type | Required | Description |
|----------|------|----------|-------------|
| `did` | `string` (did) | No | Whose forgeries to report. Defaults to the caller. ⚠ ANY DID MAY BE ASKED ABOUT, DELIBERATELY. The whole purpose of this data is to be published — `pet.trezy.shameOnYou` puts it in a public repo moments later — so treating it as a secret in transit while broadcasting it afterwards would be theatre. It also lets the server that writes the public record verify the claim for itself rather than believing a client that says 'shame this DID'. |

#### Output

**Encoding**: `application/json`

| Property | Type | Required | Description |
|----------|------|----------|-------------|
| `error` | `string` | No | Present instead of a report when there is none to give. `rejections-unavailable` means the store could not be read — which must NOT be shown as 'no forgeries', because an unreadable table would otherwise clear somebody's record by accident. |
| `message` | `string` | No |  |
| `subject` | `string` (did) | Yes | Whose report this is — echoed so a caller that omitted `did` learns which account answered. |
| `forgeries` | `array` | Yes | Empty for the overwhelming majority of accounts, and an empty array is the successful answer rather than an absence. |

### `pet.trezy.getForgeries#forgery`

**Type**: `object`

| Property | Type | Required | Description |
|----------|------|----------|-------------|
| `uri` | `string` (at-uri) | Yes |  |
| `cause` | `string` | Yes | The reason as a sentence, composed here so every copy of it agrees and none of them is written by the accused's own browser. |
| `reason` | `string` | Yes |  |
| `noticedAt` | `string` (datetime) | Yes |  |

## Raw Schema

```json
{
  "id": "pet.trezy.getForgeries",
  "defs": {
    "main": {
      "type": "query",
      "output": {
        "schema": {
          "type": "object",
          "required": [
            "subject",
            "forgeries"
          ],
          "properties": {
            "error": {
              "type": "string",
              "description": "Present instead of a report when there is none to give. `rejections-unavailable` means the store could not be read — which must NOT be shown as 'no forgeries', because an unreadable table would otherwise clear somebody's record by accident.",
              "knownValues": [
                "rejections-unavailable"
              ]
            },
            "message": {
              "type": "string"
            },
            "subject": {
              "type": "string",
              "format": "did",
              "description": "Whose report this is — echoed so a caller that omitted `did` learns which account answered."
            },
            "forgeries": {
              "type": "array",
              "items": {
                "ref": "#forgery",
                "type": "ref"
              },
              "description": "Empty for the overwhelming majority of accounts, and an empty array is the successful answer rather than an absence."
            }
          }
        },
        "encoding": "application/json"
      },
      "parameters": {
        "type": "params",
        "properties": {
          "did": {
            "type": "string",
            "format": "did",
            "description": "Whose forgeries to report. Defaults to the caller. ⚠ ANY DID MAY BE ASKED ABOUT, DELIBERATELY. The whole purpose of this data is to be published — `pet.trezy.shameOnYou` puts it in a public repo moments later — so treating it as a secret in transit while broadcasting it afterwards would be theatre. It also lets the server that writes the public record verify the claim for itself rather than believing a client that says 'shame this DID'."
          }
        }
      },
      "description": "Every record of this account's that an ingest guard refused, one entry each, with the reason written out. Reads `trezy_pet_rejections`, which the guards fill as forged records arrive on the firehose — so this is a report of what was already stopped, not a check performed now. Nothing here changes what the account may do: the refusal happened at ingest and the ledger never saw the record."
    },
    "forgery": {
      "type": "object",
      "required": [
        "cause",
        "uri",
        "reason",
        "noticedAt"
      ],
      "properties": {
        "uri": {
          "type": "string",
          "format": "at-uri"
        },
        "cause": {
          "type": "string",
          "description": "The reason as a sentence, composed here so every copy of it agrees and none of them is written by the accused's own browser."
        },
        "reason": {
          "type": "string",
          "maxLength": 64
        },
        "noticedAt": {
          "type": "string",
          "format": "datetime"
        }
      }
    }
  },
  "$type": "com.atproto.lexicon.schema",
  "lexicon": 1
}
```