Loganix Ops

Auth & Format

No API key required — this is an internal ops tool on a private network.

All request bodies must be JSON (Content-Type: application/json). All responses are JSON. Prices are returned as floats. Timestamps (created_at) are ISO 8601 strings. The updated_at field is a Unix timestamp integer — the API sets it automatically on every write; you never need to send it.

Include "changed_by" in every write body so the diff log shows who or what made the change. Use a descriptive value like "ai-agent-email-parser" or your tool name.

Also include "reason" on every write — free text explaining why the change was made and what it is based on. This is shown to the human reviewer right next to the before/after. Put whatever you based the change on here: the body of the publisher's email, a quote from their guidelines, or the URL where you found the pricing (e.g. "Publisher emailed 2026-06-24: 'raising guest post to $175'" or "Found on https://example.com/write-for-us — listed price $175"). It accepts any length of text.

How the Diff Log Works

Every write (create, update, delete, lock, unlock) does two things atomically: applies the change to publisher_sites and writes a record to publisher_sites_diff showing exactly which fields changed, what their values were before and after, and the reason the change was made.

A human can then visit /publisher-sites-review, scan each change alongside its reason, and choose one of three actions: Correct (the change was right — mark it reviewed), Edit (it was almost right — fix the values in place, which applies the correction and marks the original as edited), or Rollback (revert it — restores the record to its previous state). Edit and Rollback each log their own diff entry, so the audit trail is complete.

Returns a paginated list of publisher site records. Defaults to active sites only (inactive=0).

Query Parameters

Example

GET /api/publisher-sites?q=techcrunch&limit=10

{
  "rows": [ { ... }, { ... } ],
  "total": 42,
  "limit": 10,
  "offset": 0
}

Returns a single publisher site record by its numeric id. Returns 404 if not found.

Example

GET /api/publisher-sites/5

{
  "id": 5,
  "publisher": "webtechmania27@gmail.com",
  "website": "techmaina.com",
  "link_type": "dofollow",
  "tat": "1",
  "price_general": 80.0,
  // ... all 67 fields
}

Creates a new publisher site record. Only website and publisher are strictly required — all other fields are optional and can be added later via PATCH. Returns the new record's id and the full row as written.

Required Fields

Recommended Fields

Example Request

POST /api/publisher-sites
Content-Type: application/json

{
  "changed_by": "ai-email-parser",
  "reason": "New publisher signed up via outreach reply 2026-06-24; pricing from their email",
  "website": "example.com",
  "publisher": "owner@example.com",
  "link_type": "dofollow",
  "tat": "3",
  "price_general": 120.00,
  "permanent_link": "yes",
  "do_we_post": "yes"
}

Response (201 Created)

{
  "id": 9955,
  "row": { /* full record as saved */ }
}

Updates one or more fields on an existing record. Send only the fields you want to change — everything else stays as-is. The updated_at field is set automatically. Returns the updated full row.

Example — update pricing

PATCH /api/publisher-sites/5
Content-Type: application/json

{
  "changed_by": "ai-email-parser",
  "reason": "Publisher emailed 2026-06-24: 'bumping general posts to $95, CBD to $140 effective now'",
  "price_general": 95.00,
  "price_cbd": 140.00
}

Example — restore a deleted site

PATCH /api/publisher-sites/5
Content-Type: application/json

{
  "changed_by": "ops-dashboard",
  "inactive": 0
}

Response

{
  "id": 5,
  "row": { /* full record as saved */ }
}

Soft-deletes a site by setting inactive = 1. The record stays in the database and can be restored at any time with PATCH {"inactive": 0}. The diff log records this as a delete operation.

Request Body (optional)

DELETE /api/publisher-sites/5
Content-Type: application/json

{
  "changed_by": "ai-email-parser"
}

Response

{
  "id": 5,
  "inactive": 1
}

Sets lock_publisher = 1 on this site. A locked site is assigned exclusively to its direct publisher — vendor resellers cannot compete on it. Use this when we have confirmed the direct owner of a domain and want to protect them from vendor pricing.

Example

POST /api/publisher-sites/5/lock
Content-Type: application/json

{ "changed_by": "ai-email-parser" }

Response

{ "id": 5, "lock_publisher": 1 }

Sets lock_publisher = 0 — removes the publisher lock so vendors can compete on this site again.

Example

POST /api/publisher-sites/5/unlock
Content-Type: application/json

{ "changed_by": "ops-dashboard" }

Response

{ "id": 5, "lock_publisher": 0 }

Returns the change log. Defaults to pending (unreviewed) changes. Each row includes a changed_fields array listing every field that changed with its before and after values.

Query Parameters

Response Shape

{
  "rows": [
    {
      "id": 1,
      "ps_id": 5,
      "website": "techmaina.com",
      "publisher": "webtechmania27@gmail.com",
      "operation": "update",
      "changed_by": "ai-email-parser",
      "reason": "Publisher emailed: raising general posts to $95",
      "changed_fields": [
        { "field": "price_general", "before": 80.0, "after": 95.0 }
      ],
      "status": "pending",
      "reviewed_by": null,
      "reviewed_at": null,
      "created_at": "2026-06-24T18:00:00"
    }
  ],
  "total": 1,
  "limit": 50,
  "offset": 0
}

Marks a diff record as correct — the change was verified and no action is needed. Nothing is written to publisher_sites.

Example

POST /api/publisher-sites/diffs/1/correct
Content-Type: application/json

{ "reviewed_by": "josh@loganix.com" }

Response

{ "diff_id": 1, "status": "correct" }

Resolves a pending change by correcting the values in place — use this when the change was almost right but a value needs fixing. Applies your corrected values to the live publisher_sites row (which logs its own diff entry for the audit trail), then marks this original diff as edited. Pass only the fields you want to set under a "fields" object.

Request Body

POST /api/publisher-sites/diffs/2/edit
Content-Type: application/json

{
  "reviewed_by": "josh@loganix.com",
  "fields": {
    "price_general": 130.00
  }
}

Response

{
  "diff_id": 2,
  "status": "edited",
  "ps_id": 5,
  "row": { /* full record after the correction */ }
}

Reverts the change. Restores publisher_sites to the snapshot stored in before_json, marks the original diff as rolled_back, and logs the reversal itself as a new diff entry for audit trail purposes. Returns 400 if you try to roll back a create operation (there is no before state).

Example

POST /api/publisher-sites/diffs/1/rollback
Content-Type: application/json

{ "reviewed_by": "josh@loganix.com" }

Response

{ "diff_id": 1, "status": "rolled_back", "ps_id": 5 }