Nabla Core Server API

Name: Core Server API
Brand: Nabla Core Server API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHealthcareClinical Databearer19 EndpointsREST

Install Jentic One Beta

Connect the Core Server API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Core Server API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Core Server API.

Issue OAuth bearer tokens and per-user JWTs for clinician sessions

Provision, deactivate, and reactivate clinician user accounts and look them up by external HR ID

Stream or upload an encounter audio file to /listen for ambient transcription

GET STARTED

Start building with Core Server API

Explore with Jentic

View OpenAPI Document

For Agents

Issue user JWTs, manage clinician accounts, and run server-side ambient transcription, note generation, normalization, and patient-instruction operations on Nabla's clinical AI platform.

Use for: Create a JWT for a clinician so they can use the Nabla mobile app, Provision a new clinician user in the Nabla tenant, Listen to an encounter audio file and return a structured digest, Generate normalized clinical data such as ICD-10 codes for a recorded visit

Not supported: Does not handle billing claims submission, prescription writing, or scheduling - use for ambient transcription, clinical digest generation, normalization, and clinician user provisioning only.

Use Cases

Patterns agents use Core Server API for, with concrete tasks.

★ Ambient Scribe Integration in EHRs

Wire Nabla's ambient clinical assistant into an EHR or telehealth platform so audio captured during a visit is converted to a structured note and patient instructions. The /listen endpoint accepts encounter audio, /digest produces a structured clinical digest, and /generate_normalized_data extracts coded data such as ICD-10 entries. Replaces dictation queues and scribe services and saves clinicians several minutes per visit on documentation.

Upload the audio for visit ID 482 to POST /listen, then call POST /digest to retrieve the structured clinical digest and write it back to the EHR encounter.

Clinician User Lifecycle Management

Manage clinician user records so HR or directory changes flow into Nabla. POST /users creates a clinician, GET /users lists them, PATCH /users/{id} updates fields, /users/{id}/activate and /users/{id}/deactivate handle joining and leaving, and /users/find_by_external_id/{external_id} bridges to your HR system. Removes manual user-list reconciliation between HR, the EHR, and Nabla.

When HR offboards an employee, look up the user via GET /users/find_by_external_id/{external_id} and then call POST /users/{id}/deactivate.

JWT Issuance for Mobile and Web Clients

Server-side backends mint short-lived JWTs for individual clinicians via POST /jwt/authenticate/{user_id} so the Nabla mobile and web SDKs can act on the clinician's behalf without holding long-lived secrets. Pair with /oauth/token for the underlying server credential. Avoids embedding API keys in clients and keeps audit trails per clinician.

Call POST /jwt/authenticate/{user_id} for a clinician and return the resulting token to their authenticated mobile session.

Patient Instruction Handoff

Generate plain-language patient instructions from a recorded visit so reception or the patient portal can hand them off after the appointment. The patient-instructions operations turn the clinical encounter into a layperson summary covering medications, follow-ups, and red-flag symptoms. Useful for organisations under after-visit-summary mandates that want to reduce clinician burden.

After the digest is produced, call the patient-instructions endpoint and email the result to the patient via the portal.

AI Agent Clinical Documentation Co-Pilot

Expose Nabla server operations as Jentic tools so an AI agent embedded in a clinician's workflow can run 'transcribe this visit', 'generate the note', or 'create patient instructions' on demand. Through Jentic the bearer token stays in the encrypted vault and the agent picks the right operation across 19 endpoints via intent search. Pairs naturally with EHR-side agents that already orchestrate documentation tasks.

Search Jentic for 'generate Nabla clinical digest', execute POST /digest with the encounter ID, and post the structured note draft to the clinician's review queue.

Key Endpoints

19 endpoints — jentic publishes the only available openapi specification for nabla core server api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/oauth/token

Issue an OAuth bearer token for server access

POST

/jwt/authenticate/{user_id}

Mint a per-user JWT for clinician client apps

POST

/users

Create a new clinician user

GET

/users/find_by_external_id/{external_id}

Look up a user by external HR system identifier

POST

/listen

Submit encounter audio for ambient transcription

POST

/digest

Generate a structured clinical digest of an encounter

POST

/generate_normalized_data

Produce normalized clinical data such as ICD codes

POST

/reports

Submit an operational or usage report

POST

/oauth/token

Issue an OAuth bearer token for server access

POST

/jwt/authenticate/{user_id}

Mint a per-user JWT for clinician client apps

POST

/users

Create a new clinician user

GET

/users/find_by_external_id/{external_id}

Look up a user by external HR system identifier

POST

/listen

Submit encounter audio for ambient transcription

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Nabla server bearer token and minted user JWTs are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'generate a clinical digest from an encounter', and Jentic returns the matching Nabla operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Core Server API through Jentic.

Why is there no official OpenAPI spec for Nabla Core Server API?

Nabla does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Nabla Core Server API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Nabla Core Server API use?

The Server API uses HTTP bearer authentication. Server backends obtain an access token via POST /oauth/token and pass it in the Authorization: Bearer header. They also mint per-user JWTs via POST /jwt/authenticate/{user_id} for client-side calls. Through Jentic, both the server credential and any minted tokens stay in the encrypted vault.

How do I provision a clinician user in Nabla through the API?

POST /users creates a clinician account, PATCH /users/{id} updates fields, and POST /users/{id}/activate and /users/{id}/deactivate handle lifecycle changes. Use GET /users/find_by_external_id/{external_id} to bridge from your HR system's identifier.

Can the Nabla API turn an encounter recording into a structured note?

Yes. POST /listen accepts encounter audio for ambient transcription, POST /digest produces a structured clinical digest, and POST /generate_normalized_data returns normalized clinical data such as ICD codes. The patient-instruction operations generate the after-visit summary.

What rate limits apply to the Nabla Core Server API?

Rate limits are not declared in the OpenAPI spec. Treat the API as moderately rate-limited, implement exponential backoff on HTTP 429, and contact Nabla for committed throughput before running large historical-encounter backfills against the listen and digest operations.

How do I run a Nabla operation from an AI agent through Jentic?

Install the Jentic SDK with pip install jentic. Use SearchRequest with a query like 'generate a Nabla clinical digest' to find POST /digest, LoadRequest for its schema, and ExecutionRequest to call it. Get an agent API key through Jentic One, the self-hosted execution layer.

Can I limit what my agent is allowed to do with the Nabla Core Server API?

Yes. Because you run Jentic One yourself, your own rules decide which Nabla operations the agent may call and which credentials it may use, so you can allow digest generation from POST /digest while leaving clinician creation via POST /users out until you choose to add it. Nabla puts the clinician id directly in the URL path, as in POST /jwt/authenticate/{user_id} and GET /users/find_by_external_id/{external_id}, so a rule can pin the agent to a single user. The stored bearer token and any minted per-user JWTs are injected only at execution time and never reach the agent's prompt or logs.

Nabla Core Server API

Connect the Core Server API to your agent

Capabilities

Start building with Core Server API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs