Akismet: Introducing the official Akismet PHP SDK

For twenty years, Akismet has kept spam out of WordPress. But spammers don’t care what your site runs on and neither do we.
Last month we launched the official Akismet Drupal module. Today we’re introducing the engine that powers it: the official Akismet PHP SDK, a first-party client that brings Akismet to any PHP application.
What it is, and who it’s for
The Akismet PHP SDK is a first-party PHP client for the Akismet API. It’s built for the platforms the WordPress plugin doesn’t reach: custom apps, SaaS backends, and PHP frameworks like Laravel, Symfony, and Drupal. (The plugin is still the way to go for WordPress.)
Under the hood it’s built to feel at home in a modern PHP codebase:
- Covers the full Akismet API, from comment-check and spam/ham submissions to key verification, usage limits, and account stats.
- Works with any PSR-18 HTTP client you already have (Guzzle, Symfony HttpClient, and the like) through auto-discovery.
- Ships a typed exception hierarchy that redacts your API key, so credentials never leak into your logs.
A two-minute quick start
Install it with Composer:
composer require automattic/akismet-sdk
Then check a submission:
use AutomatticAkismetAkismet;
use AutomatticAkismetDTOContent;
use AutomatticAkismetEnumContentType;
$akismet = Akismet::create(
apiKey: 'your-api-key',
site: 'https://your-site.com',
);
$content = new Content(
userIp: $_SERVER['REMOTE_ADDR'],
userAgent: $_SERVER['HTTP_USER_AGENT'],
body: $formData['message'],
authorEmail: $formData['email'],
type: ContentType::ContactForm,
);
$result = $akismet->check($content);
if ($result->isSpam()) {
// Reject it, flag it, or queue it for review.
// $result->shouldDiscard() marks the blatant spam you can drop outright.
}
That’s the loop: build a Content object, call check(), act on the result.
Already running in production
The official Akismet Drupal module is built on this SDK. The SDK handles the API contract and type safety, while the module handles Drupal’s service wiring, queues, and moderation UI. That’s the pattern for Laravel, Symfony, and anything else you build: the SDK owns the Akismet integration and your framework owns the glue.
What’s new in 1.5.0
We have just released v1.5.0, which is about giving Akismet more to work with, and giving you more back:
- Richer content signals:
Contentnow carries the site’s language and character set, plus the surrounding conversation context, so every check has more to go on. - More insight into every verdict:
CheckResultnow surfaces the error and classification Akismet returns, so you can log and act on why something was flagged, not just whether it was. - Extended multi-site reporting: For keys that span many sites, the new extended key-sites data adds per-site metadata for cleaner reporting and account hygiene.
Get started
The SDK is open source and live on Packagist today.
- Install:
composer require automattic/akismet-sdk - Packagist: automattic/akismet-sdk
- Source and docs: github.com/Automattic/akismet-sdk-php
You’ll need an Akismet API key to make calls. Akismet’s Personal plan is pay-what-you-can and free for personal, non-commercial sites. If you’re running something commercial, pick a paid plan that matches your traffic. Either way your code stays identical, since the plan lives with your API key, not in the SDK.