API · testing

Retrieve a test result

GET /api/v2/testing/runs/{id}

Authorization

messages:read. Use a workspace-scoped bearer key or an authorized user session.

Parameters

All resource access is checked against the selected workspace and user permissions.

Name	Type	Contract
id	path · required	Resource UUID

Request

Set INBOXIT_API_KEY in your server environment. The CLI can also use an authenticated user session.

Example

curl -X GET 'https://inboxit.wtf/api/v2/testing/runs/RESOURCE_UUID' \
  -H "Authorization: Bearer $INBOXIT_API_KEY"

CLI equivalent

Use INBOXIT_TOKEN for a scoped key, or inboxit login for a user session.

Example

inboxit testing result --id RESOURCE_UUID

Response

HTTP 200. Example values are illustrative; excerpts are marked.

Example

{
  "id": "RUN_UUID",
  "status": "matched",
  "matched_id": "1",
  "extraction": {
    "codes": [
      "482951"
    ],
    "links": [
      "https://example.com/confirm"
    ],
    "code": "482951",
    "link": "https://example.com/confirm",
    "ambiguous": false,
    "untrusted_content": true
  }
}

Behavior & errors

Response excerpt. Status is waiting, matched, timed_out or cancelled. Matched response includes plain-text message. Mailbox reset returns 409; expiry returns 410 or 404 after cleanup. Does not follow extracted links. Common errors: 400 invalid input, 401 unauthenticated, 403 insufficient permission, 404 missing/inaccessible resource, 409 conflict, 429 rate/usage limit, 503 service unavailable. See Errors & retries for recovery guidance.