Use this tool to quickly generate a correct request shape, copy a cURL, and sanity-check the headers you should be sending. The response is simulated, but the request format matches the docs.
When to use this
- You are wiring up your first
POST /v1/transmissionscall. - You are not sure which scope a key needs.
- You want a reference cURL to compare against your SDK or HTTP client.
What to look for
- Authorization:
Authorization: Bearer ...should be set server-side only. - Idempotency: for create actions, set
Idempotency-Keyso retries do not duplicate work. - Content-Type:
application/jsonfor JSON bodies.
Relevant docs:
Interactive API Playground
Build a request, copy the cURL, and see a simulated response.
POSTscope: send:transmissions/v1/transmissions
curl -sS -X POST https://api.sendlib.com/v1/transmissions \
+ -H "Authorization: Bearer $SENDLIB_API_KEY" \
+ -H "Accept: application/json" \
-H "Idempotency-Key: 0d6c2a6f-3f3c-4d4a-9c1a-2f7f9c1a1f0b" \
-H "Content-Type: application/json" \
-d '{
"from": "billing@yourdomain.com",
"to": [
"user@example.com"
],
"subject": "Receipt #1042",
"html": "<p>Thanks - your receipt is attached.</p>",
"meta": {
"tenant": "acme",
"tags": [
"receipt"
]
}
}'{
"id": "tx_01HP3GZK4B8X2W1P0R9N7M6L5K",
"status": "accepted"
}