ClocknextHelp
DocumentationAPI ReferenceMCP Tools
Dashboard

Get started

OverviewQuickstart

Good to know

Response formatHandling errorsPaginating resultsSending data reliablyYour own customer idsWebhooks

API reference

Record credit POSTRecord outcome POSTComplete outcome POSTRecord wallet POSTRecord unit POSTComplete composite POST
List customers GETCreate a customer POSTGet a customer GETUpdate a customer PATCHDelete a customer DELETEGet a customer's balances GETGet a customer's wallet ledger GETSet a customer's low-balance alert PUTGet a customer's current plan GETChange a recurring grant PUTList Customer Usage Log GETLook Up Usage Logs by ID GET
Manage a customer's credit balance POSTManage a customer's outcome balance POSTManage a customer's unit balance POSTManage a customer's composite balance POSTManage a customer's wallet balance POST
List a customer's members GETAdd a member POSTUpdate a member PATCHRemove a member DELETE
PlansCreditsOutcomesUnitsComposites
List taxes GETCreate a tax POSTGet a tax GETUpdate a tax PATCH
List purchases GETCreate a purchase POSTGet a purchase GETUpdate a purchase's auto-payment setting PATCHCancel a purchase POST
List invoices GETGet an invoice GETMint a hosted pay link GET
List payments GETGet a payment GET
wallet.balance.update POSTwallet.balance.drop POST
Mint a customer-portal access token POST

API Reference

Overview

The Clocknext Payments API and Node.js SDK — meter LLM usage, manage customers and plans.

Clocknext works through the Node.js SDK and API. Both meter LLM usage — against a credit, outcome, wallet, unit, or composite — and manage customers and their plans. Every request is authenticated with an organisation-scoped API key, and every response, from either the SDK or the API, follows the same response envelope.

Base URL

https://payments.clocknext.com/api/v1

All paths in this reference are relative to this base URL — POST /signal/credit calls POST https://payments.clocknext.com/api/v1/signal/credit.

Authentication

Every request carries a per-organisation API key as a bearer token:

Authorization: Bearer cnk_your_key_here

Create, send, and rotate keys in Settings → API Keys.

The shape of every response

Success or error, every response has the same envelope:

{
  "statusCode": 200,
  "statusDetail": { "status": "SUCCESS", "message": "OK" },
  "result": { }
}

See Response format for the full contract.

Where to go next

Quickstart

Create a customer and record your first usage signal in under ten minutes.

API keys

Create an API key, send it, and rotate it safely.

Response format

The one response shape every endpoint returns.

Handling errors

Every status code the API returns and how to handle it.

Paginating results

Page through list endpoints with limit and cursor.

What you can do

AreaEndpointsWhat it's for
Signals/signal/*Record one metered request against a credit, outcome, wallet, or unit, and close a composite.
Customers/customersCreate, read, update, and delete customers; read balances and plan.
Members/customers/{id}/membersManage the people who belong to a customer.
BillingPurchases · Invoices · PaymentsSubscribe customers, read invoices, and mint hosted pay links.
Customer Portal/portal/tokenMint short-lived tokens to embed the customer portal.

Server-side only

Your cnk_… key has organisation-wide read/write access. Call this API from a server, script, or job you control — never ship the key to a browser or mobile app. To give a customer access to their own data, mint a portal token instead.

Quickstart

Create a customer, package a Plan, and record your first usage signal — start to finish.

On this page

Base URLAuthenticationThe shape of every responseWhere to go nextWhat you can do