Blog Post

Apg Vnext 51 Akismet Improved 3Rd Party Api

Apg Vnext 51 Akismet Improved 3Rd Party Api — release and upgrade information for APG vNext 51.

Upgrading APG vNext

  • Back up your SQL Server database before starting any upgrade.
  • Save your web.config, custom skins, and upfiles folder contents.
  • Run the upgrade SQL scripts in sequential order — never skip versions.
  • Test all key features after upgrading: login, posting, email notifications, file uploads.

Download & Support

APG vNext 5.1 — Akismet Anti-Spam Integration

APG vNext 5.1 introduced native Akismet support, ending the need for manual moderation of every new post on high-traffic or publicly accessible forums. Akismet is the industry-standard spam detection service used by WordPress, Discourse, and hundreds of other community platforms. Integrating it with APG vNext means new posts are silently scored before they appear, and confirmed spam never reaches the thread listing.

How Akismet Works in APG vNext

When a member submits a post, APG vNext 5.1 sends the post content, author metadata, and IP address to the Akismet API endpoint before saving it to the database. Akismet returns a binary verdict: spam or ham (not spam). If spam, the post is held in the moderation queue rather than published. The submitting member sees a generic "post is under review" message — they are never told their post was flagged as spam, which prevents spammers from trivially tuning their content to bypass the filter.

Configuration Steps

To enable Akismet in APG vNext 5.1, you need a free or paid Akismet API key (available at akismet.com — free for personal/non-commercial use). Once you have the key:

  1. Go to Admin Panel → Settings → Anti-Spam → Akismet
  2. Paste your API key into the Akismet API Key field
  3. Set Action for spam to "Hold for moderation" (recommended) or "Delete silently"
  4. Enable Log spam decisions to track false positives
  5. Click Save
<!-- web.config — Akismet endpoint and key storage -->
<appSettings>
  <add key="APG.Akismet.ApiKey"    value="your-api-key-here" />
  <add key="APG.Akismet.Enabled"   value="true" />
  <add key="APG.Akismet.Action"    value="queue" />  <!-- queue | delete -->
  <add key="APG.Akismet.LogSpam"   value="true" />
</appSettings>

Improved 3rd-Party API in APG vNext 5.1

Alongside the Akismet integration, version 5.1 significantly expanded the APG vNext REST API, making it easier to build integrations with external tools, mobile apps, and reporting dashboards.

New API Endpoints in 5.1

  • GET /api/v1/threads?forumId=&page=&pageSize= — paginated thread listing with rich metadata
  • POST /api/v1/posts — create a post programmatically (requires API key authentication)
  • GET /api/v1/members/{id}/activity — member activity timeline for dashboard widgets
  • GET /api/v1/stats — community health metrics: total posts, members online, new registrations today

API keys are generated per-user in Admin Panel → API → Manage Keys. Each key can be scoped to read-only or read-write, and IP whitelisting is supported for server-to-server integrations.

Connecting External Tools via the API

// Example: Fetch latest threads via APG vNext 5.1 API
const response = await fetch(
  'https://yourforum.com/api/v1/threads?forumId=1&pageSize=10',
  { headers: { 'X-APG-ApiKey': 'your-api-key' } }
);
const data = await response.json();
// data.threads[].title, .replyCount, .lastPostDate

Monitoring API Usage and Rate Limits

Every API response in APG vNext 5.1 includes rate limit headers so your integrations can detect when they are approaching the per-key limit and back off gracefully:

// Rate limit headers returned on every API response:
// X-RateLimit-Limit: 1000       -- requests allowed per hour
// X-RateLimit-Remaining: 876    -- requests remaining in current window
// X-RateLimit-Reset: 1719792000 -- Unix timestamp when the window resets

// When remaining hits 0, the API returns HTTP 429:
// { "error": "rate_limit_exceeded", "retry_after": 343 }

// Client-side rate limit handling:
if (response.status === 429) {
    const retryAfter = response.headers.get('Retry-After');
    await new Promise(r => setTimeout(r, retryAfter * 1000));
    return fetch(url, options); // retry
}

For integrations that need higher throughput (e.g., importing thousands of posts from another forum platform), contact APG support to request a temporary rate limit increase. Bulk imports are better handled via direct SQL Server access under a scheduled maintenance window rather than through the API.

Database Changes in APG vNext 5.1

The 5.0 → 5.1 upgrade is a minor version update with minimal database changes. The SQL upgrade script adds two tables for Akismet logging and API key management:

-- New tables added by upgrade_5.0_to_5.1.sql
CREATE TABLE apg_SpamLog (
    SpamLogID   INT IDENTITY PRIMARY KEY,
    MemberID    INT NULL,
    IPAddress   NVARCHAR(45) NOT NULL,
    PostContent NVARCHAR(MAX) NOT NULL,
    IsSpam      BIT NOT NULL,
    CheckedAt   DATETIME NOT NULL DEFAULT GETDATE()
);

CREATE TABLE apg_APIKeys (
    KeyID       INT IDENTITY PRIMARY KEY,
    MemberID    INT NOT NULL,
    APIKey      NVARCHAR(100) NOT NULL UNIQUE,
    Permissions NVARCHAR(50) NOT NULL, -- 'read' or 'readwrite'
    IPWhitelist NVARCHAR(500) NULL,
    CreatedAt   DATETIME NOT NULL DEFAULT GETDATE(),
    LastUsedAt  DATETIME NULL
);

Combining Akismet with Manual Moderation for Best Results

Akismet significantly reduces the volume of spam that reaches moderators, but it works best as one layer of a multi-layered approach. The recommended stack for a public-facing APG vNext 5.1 forum:

  1. Registration honeypot — blocks bots at registration, before they can post
  2. Email verification — ensures registrant controls the provided email address
  3. First-post queue — holds all posts from accounts with fewer than 5 posts for moderator review
  4. Akismet — machine-learning filter for posts that pass the first-post queue threshold
  5. IP blocklist — manual additions for known spam IP ranges discovered in the Akismet log

This layered approach means no single defence failure results in spam appearing on your forum. The first-post queue handles new accounts even if Akismet misclassifies them, and the IP blocklist handles repeat offenders without burning Akismet API quota on known bad actors.

Related Resources