KAGUARD

KEYAUTH API 1.3 / C++ SDK

Same SDK.
Your endpoint.

Set a KAGUARD URL in your project. Keep the KeyAuth setup you already use.

Quick setup API status
kaguard.net •••
INTEGRATION PREVIEW

Set your SDK endpoint

Use the URL in your project constructor.

ONLINE
main.cppC++
// Project endpoint
std::string url =
  "https://api.kaguard.net/api/1.3/";

KeyAuth::api client(name, ownerid,
  version, url, path);
Configured per projectAPI 1.3
BASE URLapi.kaguard.net/api/1.3/
YOUR KEYAUTH APP
⌘App nameSet in your SDK
◈Owner IDSet in your SDK
Endpoint availableKeep using your existing SDK
KEYAUTH API 1.3C++ SDKPROJECT-LEVEL URL

01 / SETUP

One URL.
That’s the change.

01

Set the endpoint

Pass the KAGUARD URL to your SDK constructor.

02

Keep your app config

Use your own KeyAuth app name, owner ID, and version.

03

Build and run

Your SDK keeps the same API 1.3 workflow.

↗

Your URL, per project

Configure each integration separately.

✓

SDK checks preserved

Signature headers pass back to your SDK.

◌

No request body logs

Cloudflare may process operational metadata.

02 / ACCESS

Plans are on the way.

Account setup and pricing are in progress.

COMING SOON

03 / FAQ

Quick answers.

Do I need to change my SDK?

No. Set the KAGUARD URL in its constructor.

Do I still need a KeyAuth account?

Yes. Use your own KeyAuth app and credentials.

Are request bodies stored?

They aren’t written to app logs. Cloudflare may process operational metadata.