Currently, GET /api/v2/messages/inbox?id_from={id} returns HTTP 404 with {"detail": "Not found"} when no messages exist with an ID greater than id_from.

According to REST standards, 404 means "this endpoint does not exist". An empty result set should return HTTP 200 with [].

This makes it impossible to distinguish between a real error (wrong endpoint, auth issue) and a normal empty inbox. Client applications are forced to handle a perfectly normal situation as a failure.

This is likely a global behavior across all API v2 endpoints that return collections, and should be addressed consistently throughout the API.

Migrated from the SMSEagle UserReport forum (2026-03-19). Legacy status: Being considered.