Documentation
Agent ToolsPOST

Agent Dmarc Generator

Generate a DMARC TXT record. Returns the DNS host to publish (`_dmarc.<domain>`), the full TXT record string, and a list of warnings (empty list if none). Use this when an agent needs to recommend or audit DMARC policy for a sender domain before validating emails from that domain. Example request: {"domain": "acme.com", "policy": "reject", "rua": ["dmarc@acme.com"]} Example response: { "host": "_dmarc.acme.com", "record": "v=DMARC1; p=reject; rua=mailto:dmarc@acme.com", "warnings": [] } Use POST /v1/agent/tools/dmarc-generator when you need this capability from your application or backend. It accepts a JSON request body. There are no query parameters for this operation.

Endpoint

Use this full URL directly in server-side integrations, scripts, or internal tooling.

POST request
https://api.dropfakes.com/api/v1/agent/tools/dmarc-generator
Full endpoint URL
POST https://api.dropfakes.com/api/v1/agent/tools/dmarc-generator

Authorization

This section explains how this endpoint should be called in the current API version.

No authorization required
This endpoint is documented as public in this version of the API reference. No bearer token is required.
Authorization
Authorization: dk_live_*****

Code examples

Start with curl, then use the language sample that matches your backend.

curl
curl -X POST "https://api.dropfakes.com/api/v1/agent/tools/dmarc-generator" \
  -H "Content-Type: application/json" \
  -d '{
  "domain": "example.com",
  "policy": "none",
  "sp": "string",
  "pct": 100,
  "adkim": "r",
  "aspf": "r",
  "rua": [
    "string"
  ],
  "ruf": [
    "string"
  ],
  "fo": "0"
}'

Parameters

Query string parameters and request body fields are listed together for faster scanning.

NameLocationTypeRequiredDescriptionDefault
domainbodystringYesBody field for `domain`.-
policybodystringNoBody field for `policy`.none
spbodystringNoBody field for `sp`.-
pctbodyintegerNoBody field for `pct`.100
adkimbodystringNoBody field for `adkim`.r
aspfbodystringNoBody field for `aspf`.r
ruabodystring[]NoBody field for `rua`.-
rufbodystring[]NoBody field for `ruf`.-
fobodystringNoBody field for `fo`.0

Success response

The primary success status for this operation is 200.

Status 200
Successful Response
200 application/json
{
  "host": "string",
  "record": "string",
  "warnings": []
}

Error response

Use this example to handle validation and request errors safely on the client or backend.

Status 422
Validation Error
422 application/json
{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}