Sending system | Ware Send

STAGE 1 · CONNECTION

Connect your installation

Define how the laboratory communicates with Ware Send.

connection.transport

HTTP APIPOST /api/v1/send

API URLPublic HTTPS · port 443 · Ware Send endpoint Bearer token

The token exists only for this execution.

requestAuthorization: Bearer <token>Content-Type: application/json

LIVE MONITORLaboratory execution

LIVE

progress0 / 0

submitted0

Accepted0

Failed0

timeout0

in-flight0

retries0

Rate0/s

latency avg0 ms

latency p95 · batch0 ms

TCP connect avg0 ms

TLS avg0 ms

TTFB avg0 ms

new / reused conn0 / 0

Elapsed00:00

accepted / second0

transportAPI

destinationEXTERNAL

endpoint/api/v1/send

securityHTTPS / Bearer

RUN DIAGNOSTICSCorrelation summary

runner ruleLocal timeout: 45s. Benchmark API uses a persistent/multiplexed pool and up to 200 workers; external traffic remains capped at 10. API makes one safe retry with the same idempotency_key. SMTP does not retry an ambiguous timeout to avoid duplicates. 202 / SMTP 250 means acceptance, not inbox delivery.

Connect your installation

Compose the test message

Choose destination and load

Real-time output

Ware Send Integration Lab