## TL;DR

400920 covers several distinct cases: RequestDenied (API call from an unauthorized IP), ReadOnlyMode (app is in read-only mode so only GETs work), NotAccessible (push is off in the app, invalid announcement parameter, or deleting a message that has a child message). Read the detail code, not just the HTTP status.

## The error

```text
decoding the 400920 / 403100 / 500910 error codes
```

## Fix

1. 400920 covers several distinct cases: RequestDenied (API call from an unauthorized IP), ReadOnlyMode (app is in read-only mode so only GETs work), NotAccessible (push is off in the app, invalid announcement parameter, or deleting a message that has a child message).
   Expected: You get the expected result; the problem is gone.
2. Re-run the original operation and confirm the error is gone.
   Expected: no error, normal output.

## When to use

- You hit this exact error with Sendbird Platform API.
- The symptom matches: decoding the 400920 / 403100 / 500910 error codes.

## When NOT to use

- A different error message from Sendbird Platform API; the cause here is specific to this error.
- Unrelated Sendbird Platform API issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Sendbird Platform API. Source: https://docs.sendbird.com/docs/chat/platform-api/v3/error-codes.

## Variant phrasings

### decoding the 400920 / 403100 / 500910 error codes

## Why it happens

Sendbird Platform API calls fail with numeric error codes like 400920, 403100, or 500910 instead of plain HTTP statuses.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.

## Source

https://docs.sendbird.com/docs/chat/platform-api/v3/error-codes