Documentation Release Notes - September 2026

September introduced a new structure for the Platform documentation, published documentation for DataSync and the new C SDK, and rewrote the Auto Moderation guide around the policy editor.

The biggest change is the new structure of the Platform docs. Pages are now organized around what you want to do, and content that isn't Platform documentation has its own tab.

DataSync is a new way to store application data on PubNub and keep every connected client up to date in real time. The new C SDK is a full rewrite of PubNub's C SDK, and the older C-Core SDK is now labeled legacy. In BizOps Workspace, Auto Moderation now works through a policy editor with three moderation features, continuing the work from August 2025 and September 2025.

Platform 🛠️​

New structure for the Platform docs​

Type: Enhancement

Until September, the Platform documentation was organized around features. Each feature owned its pages, and the same fact could appear in several places, worded differently. That works if you already know the name of the feature you need. It breaks when you arrive with a task, or when an AI assistant reads one piece of a page without the rest.

We started by writing down what was going wrong:

  • Readers couldn't quickly tell what PubNub does or find the fact they came for.
  • AI assistants returned partial answers, stale numbers, and deprecated APIs.
  • Neither could build a picture of how to design a larger application.

The new structure answers each of these:

  • Start from a goal. The Platform sidebar has 15 sections, from Getting started and Architecture to Pub/Sub, Security, and Migration guides.
  • One page, one purpose. Every page in these sections is a tutorial, a how-to, a reference, or an explanation.
  • One home for each fact. Limits and naming rules are written once and reused wherever they appear.
  • A place to begin. What is PubNub? explains what the platform does and how its capabilities fit together, and now includes an architecture diagram.

DataSync​

Type: New feature

We published documentation for DataSync. DataSync stores application data directly on PubNub and delivers every change to connected clients in real time, so you don't need an external database or your own sync layer.

DataSync is available to new accounts and to accounts that are not actively using App Context. If your keysets use App Context, keep using it. App Context remains fully supported.

You define classes for your data, and PubNub stores instances of them. Your server grants an Access Manager token, and the client app creates, reads, and subscribes to objects.

ConceptWhat it is
EntityA stored object with a JSON payload
RelationshipA typed link between two entities
ClassA versioned type definition for entities or relationships
Users, channels, membershipsBuilt-in classes that PubNub seeds for you
ProjectionA named view that controls which fields a token can read and write
DataSync eventA real-time change notification, delivered as message type 5

Creating an entity with the JavaScript SDK looks like this:

1const response = await pubnub.dataSync.createEntity({
2 id: 'product-sneaker-42',
3 class: 'Product',
4 data: {
5 classVersion: 1,
6 payload: { name: 'Retro Sneaker', price: 89.99, stock: 12 },
7 },
8})

The new pages cover the data model, data operations, events, access control, projections, schemas, and built-in types. Events are off by default and you turn them on per class version.

The SDK reference is available for JavaScript, C#, and, added later in the month, Go.

The JavaScript and C# reference pages also changed how they show code. Their DataSync, Access Manager, and Publish & Subscribe samples used to be written into the pages. They are now pulled from the SDK repositories, continuing the repository-sourced examples we introduced for Java in May 2025, several SDKs in June 2025, Unity in July 2025, PHP in October and November 2025, and Swift Chat SDK in January 2026.

Auto Moderation policy editor​

Type: Update

We rewrote the Auto Moderation guide for the new policy editor. In the product, a configuration is now a policy, and the setup wizard is replaced by one editor with a Select features sidebar. This continues the Auto Moderation documentation from August 2025 and the conflict handling we described in September 2025.

A policy combines up to three moderation features:

FeatureWhat it doesActions
Spam detectionUses AI to flag promotional spam and scam content in English-language messages. It was called Spam detection (AI).Block or report
Profanity filterNew. Analyzes messages in 15 languages and compares them to thresholds you set per category.Block or report
Word maskingReplaces words from a list with asterisks before the message reaches subscribers.Mask word

The Profanity filter covers 12 categories: toxicity, harassment, hate speech, sexual content, spam, profanity, self-harm, doxxing, scam, impersonation, raiding, and political abuse. For each one, set the sensitivity with an OFF, LOW, or HIGH slider.

Other changes in the guide:

  • Word lists: import a .txt or .csv file up to 32 KB, or click Generate to fill the list with built-in patterns for common profanity, including leet-speak variations. Auto Moderation and Channel Monitor share word lists.
  • Message path: Configure the message path once for the whole policy. By default, Auto Moderation checks the $.message.text field in your JSON payload.
  • Testing: Test the policy at any time while you edit it, with sample messages or your own text.
  • Activation: choose between Deploy as PubNub managed and Generate code for Functions. You pick keysets and channels during activation instead of in the editor. The guide now states a 30-deployment limit, and a channel pattern counts as one deployment. The previous version of the guide said 50.

If a Before Publish or Fire Function already runs on a channel, use Generate code for Functions to add moderation to it. The generated code calls ugc.moderateMessage with your policy's configId. This excerpt shows the call and the block check:

1const ugc = require('ugc');
2
3export default async (request) => {
4 try {
5 const moderationResult = await ugc.moderateMessage({
6 configId: '<YOUR_CONFIG_ID>',
7 message: request.message,
8 userId: request.params.uuid,
9 channel: request.channels[0],
10 });
11
12 if (moderationResult.flagged && moderationResult.actions.includes('block')) {
13 return request.abort('Moderated');
14 }
15
show all 20 lines

The Moderation overview now lists the three features as well.

SDKs 📦​

New C SDK​

Type: New feature

We published documentation for the new C SDK, which is now released as version 1.0.0. The source code and releases are in the pubnub/c repository.

The new C SDK is a full rewrite, not an incremental upgrade. Every public symbol changed, so existing C-Core applications can't be ported by find and replace. The migration guide for C-Core v7 lists what changed:

AreaC-Core v7New C SDK
Context lifecyclepubnub_alloc() and pubnub_free()pubnub_create() and pubnub_destroy(), or pubnub_init() and pubnub_deinit() with memory you provide
Asynchronous modelA header or build choiceOne pubnub_future_t per call, consumed with three styles chosen at each call site
Build systemMakefiles and a hand-edited pubnub_config.hCMake with full, minimal, and embedded profiles
PlatformsIncludes Microchip Harmony, Qt, and Unreal EngineA different set of targets, listed on Platform support

The C SDK also adds APIs that C-Core v7 didn't have: Files and Mobile Push for APNs and FCM.

To use the SDK, add its source tree as a CMake subdirectory in your project:

add_subdirectory(third_party/pubnub-c)
add_executable(my_app main.c)
target_link_libraries(my_app PRIVATE pubnub)

Publishing returns a future, which you consume with pubnub_await(), a callback, or cooperative polling:

static pubnub_res_t publish_hello(pubnub_context_t* ctx)
{
pubnub_future_t future = pubnub_publish(ctx,
&(pubnub_publish_opts_t){
.channel = "my_channel",
.message = "\"Hello, world!\"",
});

pubnub_res_t result = pubnub_await(future);
if (PUBNUB_OK != result) {
pubnub_string_view_t msg = pubnub_response_error_message(future);
printf("publish failed: %s - %.*s\n",
pubnub_res_str(result), (int)msg.len, msg.ptr ? msg.ptr : "");
}
pubnub_future_release(future);
show all 17 lines

The earlier C SDK is now labeled C-Core (legacy). Its documentation stays available, and each page notes that C-Core (legacy) is still supported and that new projects should use the new C SDK. The C-Core logging documentation we added in March now belongs to the legacy documentation.

Was this page useful?

Last updated on