Report a banned user

Report one identifier of a user you banned, for one category. Resubmitting the same identifier and category refreshes the entry and extends its retention. Only report bans a person reviewed, and keep the evidence under member_case_ref.

POSThttps://api.omnifence.ai/api/v1/registry/entries

Report one email of a user you banned, for one category. Report only bans that a person on your team reviewed and upheld. See Report a banned user.

Request#

Headers#

Name Type Required Description
Authorization string Yes Your API key as a Bearer token: Bearer YOUR_API_KEY.

Body (application/json)#

Field Type Required Description
identifier object Yes
identifier.type string Yes One of email.
identifier.sha256 string Yes Lowercase hex SHA-256 of the normalised email. Normalise it with the published spec first. See the Shared Registry guide.
category string Yes One of payment_fraud, prohibited_content, ban_evasion.
member_case_ref string Yes Your own case or ticket id for this ban. Needed to answer a dispute. Do not put personal data in it. Length min 1, max 200.
attest_human_review boolean Yes Confirms that a person reviewed the evidence and upheld the ban. One of true.
Example bodyJSON
{
  "identifier": {
    "type": "email",
    "sha256": "string"
  },
  "category": "payment_fraud",
  "member_case_ref": "string",
  "attest_human_review": true
}

Responses#

200 OK#

Field Type Always present Description
entry_id string (uuid) Yes
identifier_type string Yes
category string Yes One of payment_fraud, prohibited_content, ban_evasion.
member_case_ref string Yes
status string Yes One of active, disputed, revoked, expired.
has_open_dispute boolean Yes
created_at string (date-time) Yes
updated_at string (date-time) Yes
expires_at string (date-time) Yes
revoked_at null or string (date-time) Yes
revoke_reason null or string Yes
Example responseJSON
{
  "entry_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "identifier_type": "string",
  "category": "payment_fraud",
  "member_case_ref": "string",
  "status": "active",
  "has_open_dispute": false,
  "created_at": "2026-05-19T12:00:00.000Z",
  "updated_at": "2026-05-19T12:00:00.000Z",
  "expires_at": "2026-05-19T12:00:00.000Z",
  "revoked_at": "2026-05-19T12:00:00.000Z",
  "revoke_reason": "string"
}

201 Created#

Field Type Always present Description
entry_id string (uuid) Yes
identifier_type string Yes
category string Yes One of payment_fraud, prohibited_content, ban_evasion.
member_case_ref string Yes
status string Yes One of active, disputed, revoked, expired.
has_open_dispute boolean Yes
created_at string (date-time) Yes
updated_at string (date-time) Yes
expires_at string (date-time) Yes
revoked_at null or string (date-time) Yes
revoke_reason null or string Yes
Example responseJSON
{
  "entry_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "identifier_type": "string",
  "category": "payment_fraud",
  "member_case_ref": "string",
  "status": "active",
  "has_open_dispute": false,
  "created_at": "2026-05-19T12:00:00.000Z",
  "updated_at": "2026-05-19T12:00:00.000Z",
  "expires_at": "2026-05-19T12:00:00.000Z",
  "revoked_at": "2026-05-19T12:00:00.000Z",
  "revoke_reason": "string"
}