API · testing

Extract codes and links

GET /api/v2/testing/inboxes/{id}/messages/{message}/extract

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
message	path · required	Positive mailbox UID

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/inboxes/RESOURCE_UUID/messages/42/extract' \
  -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 extract --id RESOURCE_UUID --message 42

Response

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

Example

{
  "codes": [
    "482951"
  ],
  "links": [],
  "code": "482951",
  "link": null,
  "ambiguous": false,
  "untrusted_content": true
}

Behavior & errors

Extracts 4–8 digit candidates and HTTP/HTTPS links from a message in an active temporary inbox. Multiple candidates make the singular value null; maximum 30 per kind. Content is untrusted. 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.