Coming Soon Early access is currently controlled while Klckstart prepares its first public rollout.

Developer Docs

Integrate Klckstart with a cleaner, more structured developer path.

This docs layer now gives your team a proper navigation system, grouped endpoint flows, and implementation snippets for auth, billing, analytics, and admin operations.

Open API Reference Start Quickstart

Approval-aware authRegistration stays controlled until admin approval makes the account active.

Commercial modulesMove from plan catalog to events, protection, and operational workflows without losing structure.

Developer-ready layoutSticky navigation, grouped endpoints, tabs, and copy actions make implementation faster.

Quickstart

Four-step implementation path

Use this order when wiring a new product, module, or commercial workflow into Klckstart.

Confirm account state

Make registration, pending approval, activation, and suspension states explicit before building any protected flow.

Choose modules

Map whether your integration needs KlckPay, KlckShield, KlckAnalytics, or a combined dashboard experience.

Instrument actions

Track onboarding, pricing actions, billing intent, and operational events early so support and growth have visibility.

Ship with control

Keep launch control, admin notifications, and approval workflows visible before you widen public access.

Architecture

How the platform connects

This mirrors the actual product story already presented across Klckstart.

1KlckStoreIdentity + app distribution

→

2KlckSDKDeveloper integration layer

→

3KlckAnalyticsEvent + reporting visibility

→

4KlckShieldRisk review + control

→

5KlckPayBilling + entitlement actions

→

6OperationsAdmin approval + launch control

Auth

Approval-aware authentication

Registration exists, but product access only starts when admin approval marks the account active.

Core endpoints

POST /api/register.php
POST /api/login.php
POST /api/logout.php
GET /api/auth/sessions.php

Expected states

pending — created, waiting for admin
active — approved, allowed to access product pages
inactive / suspended — blocked until reviewed

Login pattern

curl -X POST https://your-domain.com/api/login.php \
  -H "Content-Type: application/json" \
  -d '{
    "email": "team@example.com",
    "password": "your-password"
  }'

const response = await fetch('/api/login.php', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  credentials: 'same-origin',
  body: JSON.stringify({ email, password })
});

const payload = await response.json();

$payload = [
    'email' => $email,
    'password' => $password,
];

// submit JSON payload to /api/login.php

Billing

KlckPay billing workflow

Keep plan discovery, payment setup, subscription creation, and recovery visible as one commercial flow.

Plan catalog

Load visible plans and module combinations before checkout begins.

GET /api/billing/plan_catalog.php

Subscription create

Create a new subscription after payment setup and module selection.

POST /api/billing/subscription_create.php

Change requests

Handle upgrades, downgrades, and next-cycle changes without breaking continuity.

POST /api/billing/subscription_change_request.php

Create a subscription

curl -X POST https://your-domain.com/api/billing/subscription_create.php \
  -H "Content-Type: application/json" \
  -b cookies.txt \
  -d '{
    "plan_id": 3,
    "payment_method_id": 18,
    "modules": ["klckpay", "klckanalytics"],
    "billing_cycle": "monthly"
  }'

await fetch('/api/billing/subscription_create.php', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  credentials: 'same-origin',
  body: JSON.stringify({
    plan_id: 3,
    payment_method_id: 18,
    modules: ['klckpay', 'klckanalytics'],
    billing_cycle: 'monthly'
  })
});

$payload = [
    'plan_id' => 3,
    'payment_method_id' => 18,
    'modules' => ['klckpay', 'klckanalytics'],
    'billing_cycle' => 'monthly',
];

// send JSON to /api/billing/subscription_create.php

Analytics + Shield

Visibility and protection together

Track meaningful actions, then route suspicious or high-risk patterns into review surfaces instead of burying them in logs.

Summary metrics

Use dashboard summary surfaces to keep product, growth, and ops aligned.

GET /api/analytics/summary.php

Track events

Emit real product events from pricing, billing, and operational entry points.

POST /api/track_event.php

Risk alerts

Review shield signals through a dedicated surface, not ad hoc logs.

GET /api/shield/alerts.php

Track an event

curl -X POST https://your-domain.com/api/track_event.php \
  -H "Content-Type: application/json" \
  -b cookies.txt \
  -d '{
    "event_name": "pricing_cta_clicked",
    "product": "klckpay",
    "page": "pricing"
  }'

await fetch('/api/track_event.php', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  credentials: 'same-origin',
  body: JSON.stringify({
    event_name: 'pricing_cta_clicked',
    product: 'klckpay',
    page: 'pricing'
  })
});

$payload = [
    'event_name' => 'pricing_cta_clicked',
    'product' => 'klckpay',
    'page' => 'pricing',
];

// send JSON to /api/track_event.php

Admin

Operational control surfaces

Admins manage approvals, lead workflows, notifications, and platform readiness before the public rollout expands.

User approval

Approve or block new registrations before they can log in.

POST /api/admin/update_user_status.php

Notification center

Surface new pending accounts and operational events for the admin team.

GET /api/admin/notifications.php

Ops overview

Keep launch control, lead flow, and operational health in one view.

GET /api/admin/ops_overview.php

Need lower-level request examples?

Move into the API Reference for endpoint-by-endpoint request and response examples.

Open API Reference