Skip to content

Developers

Wire your documents into everything you run.

A REST API for Nucleus One, API connections for Content Central, a Zapier app and an OpenAI-compatible API for Cortexa. Plain JSON over HTTPS, so any language works.

Engraved illustration: documents leave a filing cabinet, pass through a learning core and arrive on screen as organized records
Over HTTPS, any language
JSON
Nucleus One reference
OpenAPI
You create them yourself
Bearer keys
No-code triggers and actions
Zapier

01Ways in

Six ways in. Pick the one that fits the job.

No code

CapturePoint 6

Every document it captures lands in a folder with automatic naming, or in Content Central, as a searchable PDF plus a data file with every value it read.
  • Folders
  • Content Central
  • Data files

Document management

Content Central API connections

Deliver documents into Content Central and look them up from your own applications, with revocable API keys. When Content Central runs on your servers, the calls never leave your network.
  • Filing
  • Search
  • Downloads

In the cloud

Nucleus One REST API

Projects, documents, folders, tasks, forms, approvals and e-signatures, all in JSON with a published OpenAPI reference.
  • Documents
  • Tasks
  • Forms

No code

Nucleus One on Zapier

Start a Zap when a document is added to a project. Upload documents, submit forms and create tasks from thousands of other apps.
  • Triggers
  • Actions

Built with you

Custom connections

Need documents to land in a system we do not connect to yet? Our engineers plan and build the connection with you.
  • Planning
  • Build
  • Support

Private AI

Cortexa API

Private AI on servers you own, behind an OpenAI-compatible API. Point the tools and code you already use at your own server.
  • OpenAI-compatible
  • Your hardware

02First call

From sign-up to a live response.

Four steps with the Nucleus One REST API. The first call lists the organizations your key can see.

List your organizations
curl https://client-api.nucleus.one/api/v1/organizations \
  -H "Authorization: Bearer $NUCLEUS_ONE_API_KEY"
  1. 01

    Open an account

    Start Nucleus One free. Sign up and create a project to work in.

  2. 02

    Make a key

    In your user profile, open API Keys and create one. It works with your permissions.

  3. 03

    Send it

    Pass the key as a Bearer token and list the organizations you belong to.

  4. 04

    Build

    Upload documents, create tasks and read form submissions from your own systems.

03Questions

What developers ask first.

Is there an SDK?

You do not need one. Our APIs speak plain JSON over HTTPS, so the HTTP client you already use in any language works. For Nucleus One you can also generate a typed client from the published OpenAPI file with the generator you prefer.

Where is the full Nucleus One reference?

The live reference at client-api.nucleus.one/api/v1/docs lists every endpoint with its parameters and responses. The same description is published as an OpenAPI file at client-api.nucleus.one/api/v1/openapi.json.

How do I get a Nucleus One API key?

Sign in to Nucleus One, open your user profile and choose API Keys. A key acts as you, with exactly your permissions, so keep it on your server and out of browser code.

How do I connect to Content Central?

Content Central has API connections for document delivery and lookup. Content Central runs in the cloud or on your own servers, and when it runs on your servers, so do its API connections. Tell us what you want to connect and our engineers will help you set up the connection and the access it needs.

Does Cortexa work with code written for OpenAI?

Cortexa offers an OpenAI-compatible API, so tools and libraries built for that API can point at your own Cortexa server instead of a public service.

Start building

Make a key today. Build on it tonight.

Start Nucleus One free, make a key and start building right now. For Content Central and Cortexa, our engineers help you plan the integration.