Documentation
Agent ToolsPOST

Agent Spf Generator

Generate an SPF TXT record. Returns the domain host, the full TXT record string, and warnings (e.g. DNS lookup limit exceeded, record too long). Use this when an agent needs to verify or construct SPF policy for a sending domain. The `warnings` field must be checked — a non-empty list means the generated record may fail RFC 7208 compliance. Example request: {"domain": "acme.com", "includes": ["_spf.google.com"], "mx": true, "qualifier": "-all"} Example response: { "host": "acme.com", "record": "v=spf1 mx include:_spf.google.com -all", "warnings": [] } Use POST /v1/agent/tools/spf-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/spf-generator
Full endpoint URL
POST https://api.dropfakes.com/api/v1/agent/tools/spf-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/spf-generator" \
  -H "Content-Type: application/json" \
  -d '{
  "domain": "example.com",
  "includes": [
    "string"
  ],
  "ip4": [
    "string"
  ],
  "ip6": [
    "string"
  ],
  "a": false,
  "mx": false,
  "qualifier": "~all"
}'

Parameters

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

NameLocationTypeRequiredDescriptionDefault
domainbodystringYesBody field for `domain`.-
includesbodystring[]NoBody field for `includes`.-
ip4bodystring[]NoBody field for `ip4`.-
ip6bodystring[]NoBody field for `ip6`.-
abodybooleanNoBody field for `a`.false
mxbodybooleanNoBody field for `mx`.false
qualifierbodystringNoBody field for `qualifier`.~all

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"
    }
  ]
}