For developers

What Pukalani offers technically to the outside — the embed widget, the HTTP API and their limits.

This section is for everyone connecting Pukalani to something else: putting the comment widget into an existing website, or working with the HTTP API.

What there is

Embed widget

Embed comments on someone else's page — script tag or web component, without CORS configuration.

API basics

How the HTTP API is built, authentication, error format, rate limits.

What there isn't (yet)

Being honest saves you searching time:

No API keys and no machine access. The API is the interface of our own front end; authentication goes through the signed-in user's session, not through tokens for third-party systems.
No outbound webhooks.
No automatic importers from other community platforms. For now we accompany migrations by hand.
No SDK. All you need is HTTP.

Principles that apply everywhere

Everything over HTTPS, responses are JSON.
No raw HTML in content — Markdown everywhere, rendered on the server.
No tracking. The widget loads nothing from third-party servers; there are no analytics or advertising requests.
Limits live on the server. Quotas, rate limits and permissions are checked on the server, never in the browser.

Embed widget

Embed comments into any website with a script tag — attributes, comment counters, guest comments and the limits of the approach.