telnyx-email-inbound-curl

<!-- Auto-generated from Telnyx OpenAPI specs. Do not edit. --> # Telnyx Email Inbound - curl ## Installation ```text # curl is pre-installed on macOS, Linux, and Windows 10+ ``` ## Setup ```bash export TELNYX_API_KEY="YOUR_API_KEY_HERE" export TELNYX_API_BASE="https://api.telnyx.com/v2" ``` All examples below use `$TELNYX_API_KEY` for authentication. Resource IDs are UUIDs; store the IDs returned by create and list calls rather than parsing them from email addresses. ## Error Handling All API calls can fail with network errors, authentication errors (401), validation errors (422), temporary service errors (503), or rate limits (429). Capture the HTTP status separately from the JSON response in production: ```bash response_file="$(mktemp)" status="$({ curl -sS \ -o "$response_file" \ -w '%{http_code}' \ -H "Authorization: Bearer $TELNYX_API_KEY" \ "$TELNYX_API_BASE/email_inboxes"; } || printf '000')" if [[ "$status" != "200" ]]; then printf 'Telnyx request failed (HTTP %s)\n' "$status" >&2 jq . "$response_file" >&2 2>/dev/null || true fi rm -f "$response_file" ``` Common status codes: | Status | Meaning | Action | |--------|---------|--------| | `400` | Malformed request or send-time prerequisite failure | Fix the request; do not retry unchanged. | | `401` | Invalid or missing API key | Replace the key and retry. | | `403` | The account or inbox domain cannot send | Correct permissions or sending-domain configuration. | | `404` | Resource is missing, d...