76.9% of conveyancers can be impersonated. [Read]

API Quick Start

Authentication, base URLs, and your first request

5 min read API Reference

API Quick Start

Get up and running with the DMARC Busta API in minutes.

Authentication

All programmatic API requests use Bearer tokens (Personal Access Tokens):

Authorization: Bearer YOUR_API_TOKEN

Create an API Token

  1. Go to Settings → API Access
  2. Click Generate Token
  3. Give it a descriptive name (e.g., "Zapier Integration")
  4. Copy the token immediately — it won't be shown again
  5. Store it securely in your application's environment

Base URL

https://app.dmarcbusta.com/api/v1

Example Request

# List your domains
curl https://app.dmarcbusta.com/api/v1/domains \
  -H "Authorization: Bearer YOUR_API_TOKEN"

# Add a domain
curl -X POST https://app.dmarcbusta.com/api/v1/domains \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"name": "example.com"}'

Response Format

Every response is JSON, with or without an Accept header. List and detail endpoints wrap results in data plus meta; action endpoints return a success flag, a message and the affected record.

// GET /domains
{
  "data": [ { "name": "example.com", "dmarc_policy": "reject", "spf_delegated": true, ... } ],
  "meta": { "total": 5 }
}

// POST /domains
{
  "success": true,
  "message": "Domain added! Please verify ownership to unlock all features.",
  "domain": { "id": 123, "name": "example.com", "verified": false, "verification_token": "..." }
}

A domain added through the API is unverified until the ownership TXT record is published and verified in the app. Domains that belong to another account return 404, never 403, so the API does not confirm they exist.

Next Steps