QMail Two-Client GET Test Calls
GETClickable GET calls for testing the QMail send and receive lifecycle with Client1 listening on port 8081 and Client2 listening on port 8082. Every link opens in a new window and has a copy button.
@chariot.pyramid.byte
@chariot.harbor.byte
How To Use These Links
These links assume core.exe is already running for Client1 and Client2. Use the status and identity links first. For deterministic manual PING/PEEK testing, stop Client2's background beacon before sending a test mail.
Links containing REPLACE_WITH_FILE_GUID, REPLACE_WITH_TASK_ID, or REPLACE_WITH_ATTACHMENT_ID must be edited after a previous call returns the real value.
Client Readiness
Use these first to confirm both local rest_core clients are running and using the expected Mail wallet identity.
Expected SN 55076, address @chariot.pyramid.byte.
Expected SN 55077, address @chariot.harbor.byte.
Receiver Beacon Control
Stop Client2 background beacon polling before deterministic manual PING/PEEK tests, then start it again when finished.
Beacon PEEK and PING
PEEK returns quickly. PING long-polls until a Tell arrives or the timeout expires.
Split Upload then Tell
This is the main troubleshooting flow: upload first, inspect task/receipt state, then tell the receiver beacon.
Returns task_id and file_guid. Poll the task and receipt before calling Tell.
Create this local file first if you want the attachment upload to succeed: E:\Client1\qmail_test_attachment.txt
Replace the placeholder with the file_guid returned by upload.
Convenience Upload and Tell
Use this when the caller wants the API to run upload and Tell back-to-back as one async task.
Observe and Download
After upload/tell, use task status and receipts on Client1, then PEEK/download on Client2.
Replace guid with the returned file_guid.
Replace id with the returned task_id.
sender_sn can also come from the PEEK/PING notification.