API Access

Programmatic access to your Kwiro data for custom integrations, BI tools, and headless storefronts.

Headless? Custom BI? Multi-Channel? — Use the API#

Kwiro's API gives you the same data your dashboard uses, in JSON, behind a stable key you control. Available on Growth and Scale plans.

Standard REST. Bearer-token auth. JSON in, JSON out. Pull conversations, sales attribution, and memory programmatically.

Pull conversations and AI responses for custom analytics (Looker, Mixpanel, etc.)
Trigger sync from your own deploy pipeline
Embed the AI on a non-WooCommerce surface (custom checkout flow, mobile app, headless storefront)
Run BI on AI-attributed revenue, conversions, satisfaction
Webhooks for sales events, knowledge gaps, threshold crosses

Dashboard → API.
Click Generate key. The key is shown once — copy it now.
Store it in your secrets manager. We don't display it again (only the last 4 characters).
To rotate: click Regenerate. The old key dies immediately. You can have only one active key at a time.

Every request needs the Authorization header:

Authorization: Bearer kw_sk_...your_key...

Keys are scoped to your store — they can't read other stores' data.

https://api.kwiro.ai

A starter set; the full reference is published at api.kwiro.ai/docs (coming soon).

Method	Path	What
`GET`	`/v1/conversations?limit=20&before=...`	Paginated conversations
`GET`	`/v1/conversations/:id`	Full transcript
`GET`	`/v1/sales?from=...&to=...`	AI-attributed orders
`GET`	`/v1/products`	Synced products
`GET`	`/v1/memory/store`	Memory rows
`GET`	`/v1/knowledge-gaps`	Knowledge gaps

Method	Path	What
`POST`	`/v1/sync/trigger`	Force a fresh catalog sync
`POST`	`/v1/conversations/:id/feedback`	Programmatically submit feedback

Event	Fires when
`conversation.completed`	A conversation ended (idle 30 min)
`sale.attributed`	An order was AI-attributed
`knowledge_gap.detected`	A new gap crossed the frequency threshold
`threshold.crossed`	80% / 100% / cap conversation threshold

By plan:

Plan	Requests / minute
Growth	60
Scale	240

Exceeded requests get HTTP 429 with Retry-After header.

Not yet — we're prioritising the WooCommerce plugin first. The API is plain REST + JSON; any HTTP client works fine in the meantime.

Some scale customers need higher rate limits or webhook batches. Email [email protected] with your use case and we'll set up a quote.