DocsAPI Reference
Open API console

API Reference

A read-only HTTP API for pulling your projects, usage and conversation metadata into your own systems — a warehouse, a dashboard, a scheduled report, or an automation in Zapier or n8n.

What you can do with it

The API exposes what Nubo already records about your chatbots: which projects exist, how much they are being used, which models served which replies, and per-conversation metadata. Everything is scoped to the workspace that owns the API key you present.

Read-only, on purpose

Every endpoint is a GET. There is no way to send a chat message, create a project or change a setting through this API — those stay in the Nubo portal, where they are covered by your plan limits and audit trail.

Message content is never exposed. Nubo does not persist the text of conversations, so sessions come back as metadata — timings, token counts, models, tool calls — and not transcripts.

Base URL

Base URL
https://api.nubo-chat.com

Every path in this reference is relative to that host and begins with /v1. The version segment is part of the contract: a future /v2 would run alongside /v1 rather than replacing it under you.

Your first request

Create a key on the Developer page in the Nubo portal, then send it on the X-API-Key header:

cURL
curl -H "X-API-Key: nubo_your_key_here" \
  https://api.nubo-chat.com/v1/projects
Response
[
  {
    "id": "8f14e45f-ceea-467a-9ae4-2c1e2f0f1a3b",
    "name": "Support Bot",
    "isActive": true,
    "createdAt": "2026-03-11T09:22:41Z",
    "isDefault": true
  }
]

The first call of the day can be slow

The database behind the API pauses when idle. A request arriving after a quiet period can take up to a minute while it resumes. Set a generous timeout and retry rather than treating it as an outage — subsequent calls are fast.

Postman collection

All nine endpoints, pre-wired with authentication and example responses. Import it, paste your key into the apiKey variable, and every request works.

Download the collection

In Postman: Import → drop the file in → open the collection's Variables tab → set apiKey. Authentication is inherited by every request, so there is no per-request header to set. Fill projectId and sessionId from the responses to List projects and List sessions to make the single-item requests work.

Usable before you have a key

Every request ships with saved example responses, so you can read the exact shapes without calling anything. Point Postman's mock server at the collection and you can build and test your integration against realistic data before wiring up the real API.

Interactive console

The complete machine-readable contract — every parameter, every response field, every status code — is published as an OpenAPI document, with a console you can call live using your own key:

These pages cover the concepts the contract cannot express on its own: how keys behave, how scoping works, what the limits are, and how to poll without missing data. For the exact shape of any single response, the console is the source of truth.

Where to go next