Behold! The new and improved Twitter API v2 404: a 200 OK with errors in the response body.

gistfile1.txt

200 OK
Cache-Control: no-cache, no-store, max-age=0
Date: Fri, 23 Apr 2021 15:01:18 GMT
Server: tsa_a
Content-Length: 263
Content-Type: application/json; charset=utf-8
Content-Disposition: attachment; filename=json.json
Set-Cookie: personalization_id="v1_JE0Wf+QnkgraRUU2FloMsw=="; Max-Age=63072000; Expires=Sun, 23 Apr 2023 15:01:18 GMT; Path=/; Domain=.twitter.com; Secure; SameSite=None
Set-Cookie: guest_id=v1%3A161919007878889378; Max-Age=63072000; Expires=Sun, 23 Apr 2023 15:01:18 GMT; Path=/; Domain=.twitter.com; Secure; SameSite=None
Strict-Transport-Security: max-age=631138519
X-Access-Level: read-write
X-Connection-Hash: 293506d2f3beb8ac5f652c588b947f1f
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-Rate-Limit-Limit: 15
X-Rate-Limit-Remaining: 14
X-Rate-Limit-Reset: 1619190978
X-Response-Time: 36
X-Xss-Protection: 0

{
   "errors" : [
      {
         "detail" : "Could not find user with id: [1122334455667788].",
         "parameter" : "id",
         "resource_id" : "1122334455667788",
         "resource_type" : "user",
         "title" : "Not Found Error",
         "type" : "https://api.twitter.com/2/problems/resource-not-found",
         "value" : "1122334455667788"
      }
   ]
}

Body reformatted, above, for clarity.