Advancedcomputersoft Docman 10 PEPR Integration API

Name: Docman 10 PEPR Integration API
Brand: Docman 10 PEPR Integration API
Availability: InStock

Browse all Swaggerhub Advancedcomputersoft APIs

★ Only Publicly Available OpenAPI DocumentCRMContact Managementbearer5 Endpoints

Install Jentic One Beta

Connect the Docman 10 PEPR Integration API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Docman 10 PEPR Integration 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 Docman 10 PEPR Integration API.

Request bearer token

Document with metadata by reference

Get task count for a user

Query and filter Docman 10 PEPR Integration API records by parameters

GET STARTED

Start building with Docman 10 PEPR Integration API

Explore with Jentic

View OpenAPI Document

For Agents

Programmatically request bearer token, document with metadata by reference. Covers 5 operations with bearer authentication.

Use for: I need to request bearer token, I want to document with metadata by reference, Search for documents with completed tasks, Find all document task comments

Not supported: Does not handle payments, communications, or developer tools - use for crm only.

Use Cases

Patterns agents use Docman 10 PEPR Integration API for, with concrete tasks.

★ CRM Operations

Use the Docman 10 PEPR Integration API to perform crm operations programmatically. The API provides 5 endpoints covering core functionality including request bearer token, document with metadata by reference, documents with completed tasks.

Call POST /token to request bearer token

Automated Authentication Management

Automate authentication operations by combining multiple Docman 10 PEPR Integration API endpoints. Agents can document with metadata by reference and then documents with completed tasks in a single workflow.

Call GET /api/tenants/{odsCode}/patients/reference/{patientRef}/Documents/{documentGuid} to document with metadata by reference, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Docman 10 PEPR Integration API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Search Jentic for 'request bearer token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

5 endpoints — docman 10 api features to allow university hospital birmingham's pepr system to pull in triaged referral letters and user task counts.

METHOD

PATH

DESCRIPTION

POST

/token

Request bearer token

GET

/api/tenants/{odsCode}/patients/reference/{patientRef}/Documents/{documentGuid}

Document with metadata by reference

GET

/api/tenants/{odsCode}/documents/task-updates

Documents with completed tasks

GET

/api/tenants/{odsCode}/discussions/task-comments/{documentGuid}

Document task comments

GET

/api/tenants/{odsCode}/discussions/task-count

Get task count for a user

POST

/token

Request bearer token

GET

/api/tenants/{odsCode}/patients/reference/{patientRef}/Documents/{documentGuid}

Document with metadata by reference

GET

/api/tenants/{odsCode}/documents/task-updates

Documents with completed tasks

GET

/api/tenants/{odsCode}/discussions/task-comments/{documentGuid}

Document task comments

GET

/api/tenants/{odsCode}/discussions/task-count

Get task count for a user

Why Jentic?

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

Credential isolation

Your Docman 10 PEPR bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'request a bearer token' or 'get task updates for a tenant', and Jentic returns the matching Docman 10 PEPR 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 Docman 10 PEPR Integration API through Jentic.

What authentication does the Docman 10 PEPR Integration API use?

The Docman 10 PEPR Integration API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I request bearer token with the Docman 10 PEPR Integration API?

Yes. Use the POST /token endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Docman 10 PEPR Integration API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I request bearer token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'request bearer token'. Jentic returns the matching Docman 10 PEPR Integration API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Docman 10 PEPR Integration API have?

The Docman 10 PEPR Integration API exposes 5 endpoints covering authentication, documents, discussions operations.

Can I limit what my agent is allowed to do with the Docman 10 PEPR Integration API?

Yes. Because you run Jentic One yourself, your own rules decide which of the five operations the agent may call and which bearer token it uses, so you can grant only the reads you want, such as GET Documents by reference or GET task-updates, while withholding the POST /token call. The tenant ods code lives in the URL path (/api/tenants/{odsCode}/...), so a rule can pin the agent to a single tenant for its document and task lookups. Since this integration's document and discussion endpoints are read-only, the agent can only retrieve the referral letters, task comments, and task counts you allow, never modify them.

Advancedcomputersoft Docman 10 PEPR Integration API

Connect the Docman 10 PEPR Integration API to your agent

Capabilities

Start building with Docman 10 PEPR Integration API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs