Get post report reasons

The "get post report reasons" API allows users to retrieve a list of available report reasons for a post. This can help to provide context for users who want to report a post and ensure that they select an appropriate reason.

Query Parameters

client_auth_token string required

Client API token

Responses

• 200
• 401

---

OK

Response Headers

application/json

Schema

Example (from schema)

Example 1

Example

---

Schema

success boolean
abuses_options string[]

list of report reasons

{
  "success": true,
  "abuses_options": [
    "string"
  ]
}

{
  "success": true,
  "abuses_options": [
    "Offensive language",
    "Inappropriate content",
    "Other"
  ]
}

{
  "success": true,
  "abuses_options": [
    "Offensive language",
    "Inappropriate content",
    "Other"
  ]
}

Unauthorized response, api will respond with this 401 eithr user is not logged in or do not have permission to perform some action. Like creating a post in a room, but user is not member of room.

System will also return 401 if api token is missing or invlaid.

application/json

Schema

Example (from schema)

not logged in

missing or invalid api key

---

Schema

errors string[]
status integer

Default value: 401

success boolean

Default value: false

{
  "errors": [
    "string"
  ],
  "status": 401,
  "success": false
}

{
  "errors": [
    "You need to sign in or sign up before continuing."
  ],
  "success": false
}

{
  "message": "You don't have permission!",
  "status": 401,
  "success": false
}

Loading...