34 uç · /api/mail/v1/domains
İstek örnekleri ucun GERÇEK metodu ve yolundan üretilir. 34 ucun elle doğrulanmış gövde örneği henüz yok; o uçlarda iskelet gövdesizdir — uydurma bir alan yazmıyoruz.
idcurl -X PUT "https://{slug}.bmail.blesyum.app/api/mail/v1/domains/<id>/bimi" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"{
"data": "…",
"trace_id": "01JC…"
}idcurl -X POST "https://{slug}.bmail.blesyum.app/api/mail/v1/domains/<id>/dkim/rotate" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"{
"data": "…",
"trace_id": "01JC…"
}idcurl -X GET "https://{slug}.bmail.blesyum.app/api/mail/v1/domains/<id>/dmarc-forensic" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"{
"data": "…",
"trace_id": "01JC…"
}id(orijinal-mesaj alıcı/konu/gövde ASLA). Gövde = ham RFC 6591 AFRF raporu. Reported-Domain hedefle eşleşmeli (cross-domain guard).
curl -X POST "https://{slug}.bmail.blesyum.app/api/mail/v1/domains/<id>/dmarc-forensic" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"{
"data": "…",
"trace_id": "01JC…"
}idforward eder → RFC 7489 Ek-C XML ayrıştır + MF11 ingest. Gövde = ham rapor XML'i (String). Raporun `policy_published/domain`'i hedef domain ile eşleşmeli (cross-domain karışma yok).
curl -X POST "https://{slug}.bmail.blesyum.app/api/mail/v1/domains/<id>/dmarc-report" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"{
"data": "…",
"trace_id": "01JC…"
}idcurl -X PUT "https://{slug}.bmail.blesyum.app/api/mail/v1/domains/<id>/inbound-policy" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"{
"data": "…",
"trace_id": "01JC…"
}idcurl -X GET "https://{slug}.bmail.blesyum.app/api/mail/v1/domains/<id>/mta-sts" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"{
"data": "…",
"trace_id": "01JC…"
}idyeni politikayı çeker); DNS'e yeni id yayınlanması (müşteri/CF) canlı-etki için gereklidir (MF16).
curl -X PUT "https://{slug}.bmail.blesyum.app/api/mail/v1/domains/<id>/mta-sts" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"{
"data": "…",
"trace_id": "01JC…"
}idcurl -X PUT "https://{slug}.bmail.blesyum.app/api/mail/v1/domains/<id>/over-quota-action" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"{
"data": "…",
"trace_id": "01JC…"
}idownership/SPF/DKIM/DMARC/MTA-STS/TLS-RPT durumunu CANLI (hickory) DNS'e karşı değerlendirir → GO/WARN/FAIL. `/verify` tekil-aktive-eder; bu uç YALNIZ salt-okunur go/no-go raporu (kesim-kararı, yan-etkisiz). Beklenen kayıtlar `/dns` ile AYNI config'ten üretilir (tutarlı: müşteriye söylediğimiz kayıtlara karşı kontrol). `cutover_readiness` çekirdeği (readiness.rs) tamamen test'li; bu uç onu canlı resolver'la ERİŞİLEBİLİR kılar.
curl -X GET "https://{slug}.bmail.blesyum.app/api/mail/v1/domains/<id>/readiness" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"{
"data": "…",
"trace_id": "01JC…"
}idoranı + DMARC-hizalama + TLS-başarı metrikleri + varsayılan-eşik alarm değerlendirmesi.
curl -X GET "https://{slug}.bmail.blesyum.app/api/mail/v1/domains/<id>/reputation" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"{
"data": "…",
"trace_id": "01JC…"
}idcurl -X GET "https://{slug}.bmail.blesyum.app/api/mail/v1/domains/<id>/reputation-thresholds" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"{
"data": "…",
"trace_id": "01JC…"
}curl -X PUT "https://{slug}.bmail.blesyum.app/api/mail/v1/domains/<id>/reputation-thresholds" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"{
"data": "…",
"trace_id": "01JC…"
}idcurl -X DELETE "https://{slug}.bmail.blesyum.app/api/mail/v1/domains/<id>/reputation-thresholds" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"{
"data": "…",
"trace_id": "01JC…"
}idcurl -X GET "https://{slug}.bmail.blesyum.app/api/mail/v1/domains/<id>/retention-history" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"{
"data": "…",
"trace_id": "01JC…"
}ideder → RFC 8460 JSON ayrıştır + MF11 ingest. Gövde = ham rapor JSON'u (String; en son extractor). Raporun yalnız bu domain'e ait politikaları kaydedilir (cross-domain karışma yok).
curl -X POST "https://{slug}.bmail.blesyum.app/api/mail/v1/domains/<id>/tls-rpt" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"{
"data": "…",
"trace_id": "01JC…"
}idTXT-challenge + gerçek DNS lookup çekirdeği (`verify::verify_domain`/`verify_and_persist`) hazırdı; bu uç onu ERİŞİLEBİLİR kılar (kullanıcı "şimdi doğrula"). Periyodik toplu-sweep = scheduler (MF3/16).
curl -X POST "https://{slug}.bmail.blesyum.app/api/mail/v1/domains/<id>/verify" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"{
"data": "…",
"trace_id": "01JC…"
}idcurl -X GET "https://{slug}.bmail.blesyum.app/api/mail/v1/domains/<id>/warmup" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"{
"data": "…",
"trace_id": "01JC…"
}idcurl -X PUT "https://{slug}.bmail.blesyum.app/api/mail/v1/domains/<id>/warmup-exempt" \
-H "Authorization: Bearer <oturum-token>" \
-H "Accept: application/json"{
"data": "…",
"trace_id": "01JC…"
}