Official Sinch API skills for AI coding agents — SMS, Voice, Verification, Numbers, Mailgun email, and more.
71
89%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Base path: /v1/dmarc/
Requires a DMARC DNS record configured on the domain before report data becomes available.
| Endpoint | Method | Description |
|---|---|---|
/v1/dmarc/setup | GET | Check if DMARC reporting is set up for the account |
/v1/dmarc/records/{domain} | GET | Retrieve DMARC DNS records for configuration |
/v1/dmarc/referral | POST | Get referral link to Redsift DMARC dashboard (body: { "email": "..." }) |
/v1/dmarc/domains | GET | Aggregate DMARC data for all domains |
/v1/dmarc/domains/{domain} | GET | DMARC data for a single domain |
/v1/dmarc/domains/{domain}/s/{source} | GET | Drill down by sending source |
/v1/dmarc/domains/{domain}/s/{source}/h/{host} | GET | Drill down by host within a source |
/v1/dmarc/domains/{domain}/s/{source}/h/{host}/ip/{ip} | GET | Drill down to a specific sending IP |
DMARC data follows a hierarchy for progressive investigation:
domains → domains/{domain} → .../s/{source} → .../h/{host} → .../ip/{ip}Start with the domain-level view, then drill into sources, hosts, and IPs to identify which infrastructure is failing DMARC alignment.
GET /v1/dmarc/setupGET /v1/dmarc/records/{domain}v=DMARC1; p=none; ...)GET /v1/dmarc/domains/{domain}skills
sinch-10dlc
references
sinch-authentication
sinch-conversation-api
sinch-elastic-sip-trunking
references
sinch-fax-api
sinch-imported-numbers-hosting-orders
references
sinch-in-app-calling
sinch-mailgun
references
sinch-mailgun-inspect
references
sinch-mailgun-optimize
references
sinch-mailgun-validate
sinch-number-lookup-api
sinch-number-order-api
sinch-numbers-api
references
sinch-porting-api
sinch-provisioning-api
sinch-sdks
sinch-verification-api