KAGUARDKEYAUTH SDK

KEYAUTH API 1.3 / SDK ENDPOINT

Your SDK.
Your endpoint.

Set a KAGUARD URL in your project and keep your existing KeyAuth setup.

Get started API status
✓ KeyAuth API 1.3 ✓ Set per project
kaguard.net •••
PROJECT SETTINGS

API endpoint

ONLINE
BASE URL KEYAUTH API 1.3
https://api.kaguard.net/api/1.3/
SDKC++SetupPer project
Endpoint availableAPI 1.3
✦ KeyAuth API 1.3
</> Works with your SDK
MADE FOR YOUR STACK ✳ KeyAuth API 1.3 </> C++ SDK ↗ Custom endpoint

01 / QUICK SETUP

One URL.
That’s the change.

Pass the endpoint to your SDK constructor. Your KeyAuth app settings stay in your project.

See what’s included
PROJECT CONFIGKeyAuth SDK
C++
// Set your endpoint
std::string url =
  "https://api.kaguard.net/api/1.3/";

KeyAuth::api client(name, ownerid,
  version, url, path);
Configured in your application✓

02 / BUILT FOR YOUR WORKFLOW

Everything stays
right where you expect.

01↗

Your project, your URL.

Choose an endpoint in each SDK setup.

api.kaguard.net /api/1.3/
02✓

SDK checks stay intact.

Signature headers pass back to your SDK.

03◌

Request bodies aren’t logged.

Cloudflare may process operational metadata.

03 / ACCESS

Plans are on the way.

Account setup and pricing are in progress.

COMING SOON

04 / 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.