Link building API. Your links, prospects and outreach in your own tools.

Four endpoints, four MCP tools

Each endpoint is a POST to /rest/v1/<endpoint> on app.marketingtracer.com. In your AI assistant the same data is the MCP tool under each endpoint.

Every endpoint takes site_id. linkbuilding.links takes stage, limit (1 to 5,000, default 100) and cursor; linkbuilding.overview takes month (YYYY-MM) for a report of an earlier month.

A live link that went missing, as the API returns it

curl -X POST https://app.marketingtracer.com/rest/v1/linkbuilding.links \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"site_id": "YOUR_SITE_ID", "stage": "live", "limit": 1}'

From a real account, with the sites and ids changed and shortened where you see …:

{
  "data": [{
    "id": "6ae03f867a2162526408e976",
    "url": "https://news.example.org/article/css-tricks-is-back",
    "domain": "news.example.org",
    "stage": "live",
    "email": "hello@example.org",
    "contact_form": "https://example.org/contact",
    "added_at": "2026-10-27T06:07:02Z",
    "live_at": "2026-10-30T12:49:47Z",
    "check": {
      "state": "missing",
      "last_at": "2026-10-30T13:50:01Z",
      "next_at": "2026-11-01T02:50:01Z",
      "found": null,
      "history": [{"at": "2026-10-30T13:50:01Z", "result": "missing"}]
    },
    …
  }],
  "meta": {"site_id": "YOUR_SITE_ID", "next_cursor": "6ae03f867a2162526408e976", "total": 8}
}

This one is worth a look: it was marked live, but our first check did not find the link on the page. It counts as lost only after two checks in a row that don't find it. A page that doesn't load doesn't count as a miss, so a site that is down for a day doesn't set off an alarm.

Every endpoint, argument and field

Generated from the same definitions the API itself runs on, and the example answers are tested against them, so this reference is never behind. Every endpoint is a POST with a JSON body; reading endpoints also take a GET with the same arguments in the query string. Send your API key as Authorization: Bearer YOUR_API_KEY. Every answer is {"data": …, "meta": {…}}: meta.site_id always, meta.next_cursor and meta.total for a list, meta.period where the endpoint covers a period. An error is {"error": {"code", "message"}} with the HTTP status: 400 invalid_argument, unknown_argument or missing_argument; 401 not_authenticated; 403 no_access or tool_off; 404 not_found; 429 rate_limited. The machine-readable version is openapi.json.

linkbuilding.overview

POST /rest/v1/linkbuilding.overview · MCP tool get_linkbuilding_overview

Returns the link building results of one site: live and lost links, links won and lost per month (12 months up to month), how far the prospects added in the last 90 days got (found, contacted, agreed, live), what needs attention, and the anchor texts of the live links.

Arguments

Example request

curl -X POST https://app.marketingtracer.com/rest/v1/linkbuilding.overview \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"site_id":"YOUR_SITE_ID"}'

Example response · A real answer, anonymised and shortened to two items per list.

{
  "data": {
    "month": "2026-10",
    "kpis": {
      "live": 8,
      "lost": 1,
      "waiting": 4,
      "follow": 0,
      "checked": 0,
      "nofollow": 0,
      "new_this_month": 1,
      "lost_this_month": 0,
      "follow_pct": null
    },
    "months": [{"month": "2026-09", "new": 0, "lost": 0}, {"month": "2026-10", "new": 1, "lost": 0}],
    "funnel_90_days": {"found": 45, "sent": 2, "agreed": 2, "live": 1},
    "attention": {"lost": [], "agreed_old": [], "changed": [], "mails_next_24h": 0},
    "anchors": [
      {"anchor": "example text", "count": 2, "share_pct": 40},
      {"anchor": "more text", "count": 1, "share_pct": 20}
    ],
    "smtp_ready": false
  },
  "meta": {"site_id": "YOUR_SITE_ID"}
}

Response fields · in data:

linkbuilding.links

POST /rest/v1/linkbuilding.links · MCP tool get_linkbuilding_links

Returns the links and prospects of one site, newest first: the page, its domain, the stage (found, sent = contacted, agreed, live, lost, rejected), the contact found, what our own check last saw on the page (is the link there, the anchor, follow or nofollow) and the state of the outreach mails.

Arguments

Example request

curl -X POST https://app.marketingtracer.com/rest/v1/linkbuilding.links \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"site_id":"YOUR_SITE_ID","limit":2}'

Example response · A real answer, anonymised and shortened to two items per list.

{
  "data": [
    {
      "id": "6ae43406b841f35e0f0d9c95",
      "url": "https://news.example.org/articles/rail-grant",
      "domain": "news.example.org",
      "status": "agreed",
      "stage": "agreed",
      "my_url": null,
      "anchor": null,
      "tag": "critical css",
      "note": null,
      "email": null,
      "contact_form": "https://news.example.org/contact",
      "contact_queued": false,
      "contact_checked_at": "2026-10-30T12:48:34Z",
      "added_at": "2026-10-30T06:07:02Z",
      "status_at": "2026-10-30T12:49:44Z",
      "live_at": null,
      "check": {
        "state": null,
        "last_at": null,
        "next_at": "2026-10-31T12:49:44Z",
        "found": null,
        "history": [],
        "changes": []
      },
      "mail": {
        "sequence_id": null,
        "step": 0,
        "next_at": null,
        "last_at": null,
        "stopped": null,
        "error": null
      }
    },
    {
      "id": "6ae2e285b195fcf9b00f6244",
      "url": "https://m.example.net/news/report/css-officers",
      "domain": "m.example.net",
      "status": "open",
      "stage": "found",
      "my_url": null,
      "anchor": null,
      "tag": "critical css",
      "note": null,
      "email": null,
      "contact_form": "https://example.net/contact",
      "contact_queued": false,
      "contact_checked_at": "2026-10-30T12:48:30Z",
      "added_at": "2026-10-29T06:07:01Z",
      "status_at": null,
      "live_at": null,
      "check": {
        "state": null,
        "last_at": null,
        "next_at": null,
        "found": null,
        "history": [],
        "changes": []
      },
      "mail": {
        "sequence_id": null,
        "step": 0,
        "next_at": null,
        "last_at": null,
        "stopped": null,
        "error": null
      }
    }
  ],
  "meta": {"site_id": "YOUR_SITE_ID", "next_cursor": "6ae2e285b195fcf9b00f6244", "total": 958}
}

Response fields · data is a list; each item has:

linkbuilding.sequences

POST /rest/v1/linkbuilding.sequences · MCP tool get_linkbuilding_sequences

Returns the outreach sequences of one site: a first mail and up to two follow-ups after a number of working days, with how many sites were contacted with it and how many agreed.

Arguments

Example request

curl -X POST https://app.marketingtracer.com/rest/v1/linkbuilding.sequences \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"site_id":"YOUR_SITE_ID"}'

Example response · Illustrative: the account we sampled had no sequences or scheduled mails; the fields are as the code returns them.

{
  "data": [
    {
      "id": "seq1",
      "name": "Resource pages",
      "steps": [
        {
          "subject": "A resource for your readers",
          "body": "Hi [voornaam], I read [partner_link] …",
          "after_workdays": 0
        },
        {
          "subject": "",
          "body": "Hi [voornaam], a quick follow-up …",
          "after_workdays": 4
        }
      ],
      "contacted": 12,
      "agreed": 3
    }
  ],
  "meta": {"site_id": "YOUR_SITE_ID", "next_cursor": null, "total": 1}
}

Response fields · data is a list; each item has:

linkbuilding.queue

POST /rest/v1/linkbuilding.queue · MCP tool get_linkbuilding_queue

Returns the outreach mails scheduled for one site, sent through the site's own mail server on working days, and how many went out today against the daily limit.

Arguments

Example request

curl -X POST https://app.marketingtracer.com/rest/v1/linkbuilding.queue \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"site_id":"YOUR_SITE_ID"}'

Example response · Illustrative: the account we sampled had no sequences or scheduled mails; the fields are as the code returns them.

{
  "data": {
    "sent_today": 3,
    "day_limit": 25,
    "scheduled": [
      {
        "link_id": "6ae43406b841f35e0f0d9c95",
        "domain": "news.example.org",
        "email": "editor@example.org",
        "sequence_id": "seq1",
        "sequence": "Resource pages",
        "step": 1,
        "send_at": "2026-11-02T09:10:00Z",
        "error": null
      }
    ]
  },
  "meta": {"site_id": "YOUR_SITE_ID"}
}

Response fields · in data: