API Documentation

1. Overview

The Mad Ad Slingers API (v1) lets account holders work with their leads, campaigns, and analytics programmatically. List records, create leads and draft campaigns, move leads and campaigns through their statuses, and pull headline performance metrics — the same endpoints power integrations like our Zapier app, which connects Mad Ad Slingers to thousands of other tools.

All requests and responses are JSON. List endpoints return records newest first, and lead, campaign, and analytics responses wrap their payload in a data field.

2. Base URL

Every endpoint on this page is relative to:

https://mad-ad-slingers.online/api/v1

3. Authentication

The API uses API-key authentication. Send your key on every request in the X-API-Key header:

X-API-Key: mas_live_YOUR_KEY

Getting a key. API keys are available to Mad Ad Slingers account holders and are issued by the Mad Ad Slingers team — ask your agency admin for a key with the scopes you need. Live keys start with mas_live_.

Scopes. Each key carries one or more scopes that control what it can do:

• read — list and fetch records, and run the /me key check.
• write — create leads and campaigns, and update statuses.
• analytics — required for the analytics summary endpoint.
• webhooks — issued for webhook delivery setups.

Verify a key. Call GET /me (documented below). It works with any scope and returns the record for the key you sent, so you can confirm a key is valid before wiring up an integration.

Treat your key like a password: keep it server-side, never embed it in client-side code or public repositories, and ask us to rotate it if it is ever exposed.

4. Endpoints

Account

Leads

Lead object fields:

Campaigns

Campaign object fields:

Analytics

5. Example Request & Response

List the 10 most recent leads:

curl https://mad-ad-slingers.online/api/v1/leads?limit=10 \
  -H "X-API-Key: mas_live_YOUR_KEY"

Response:

{
  "data": [
    {
      "id": 12345,
      "business_id": 7,
      "first_name": "Jane",
      "last_name": "Doe",
      "full_name": "Jane Doe",
      "email": "jane.doe@example.com",
      "phone": "+15551234567",
      "company": "Acme Plumbing Co.",
      "position": "Owner",
      "industry": "Home Services",
      "website": "https://acmeplumbing.example.com",
      "linkedin": "https://www.linkedin.com/in/janedoe",
      "status": "new",
      "stage": "new",
      "score": 82,
      "source": "api",
      "quality": "high",
      "city": "Austin",
      "state": "TX",
      "created_at": "2026-10-01T14:22:31Z",
      "updated_at": "2026-10-01T14:22:31Z"
    }
  ]
}

Create a lead:

curl -X POST https://mad-ad-slingers.online/api/v1/leads \
  -H "X-API-Key: mas_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"first_name": "Jane", "last_name": "Doe", "email": "jane.doe@example.com", "company": "Acme Plumbing Co."}'

6. Errors

Failed requests return a standard HTTP error status (400 or above) with a JSON body containing a detail field describing the problem:

{
  "detail": "<error message>"
}

• 401 / 403 — the API key is missing, invalid, or does not carry the scope the endpoint requires (for example, calling a create endpoint with a read-only key).
• Other 4xx — the request itself was rejected, for example a lead create without a valid email address.
• 5xx — a server-side problem; the detail field carries the message returned by the API.

7. Support

Questions about the API, or need a key issued or rotated? Email hello@mad-ad-slingers.com.