canonical: https://jentic.com/apis/swaggerhub.advancedcomputersoft/docman-10-pepr-integration-api

# Advancedcomputersoft Docman 10 PEPR Integration API

Docman 10 API features to allow University Hospital Birmingham's PEPR system to pull in triaged referral letters and user task counts. <p> Your organisation requires the PEPR API claim in order to use these operations. Please contact your account manager in order to arrange access. The API exposes 5 endpoints secured with bearer authentication.

## For AI agents

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

## Scope

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

## Capabilities

- 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
- Monitor Docman 10 PEPR Integration API operational status and events

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

| 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 |

## Key resources

- **Authentication** — Operations for authenticating with the Docman 10 API
- **Documents** — Operations relating to patient documents in Docman 10 and RMS
- **Discussions** — Operations relating to discussions about patient referrals in Docman RMS

## Why Jentic

- **Setup:** Wiring the Docman 10 PEPR Integration API by hand means calling /token for a bearer token, attaching it to every request, and threading the tenant ods code through each document and task call yourself. Through Jentic you install once, import the Docman 10 PEPR Integration API from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** The PEPR API puts the tenant ods code in the URL path (/api/tenants/{odsCode}/...), so a rule can pin your agent to one tenant for its document and task-update reads. You choose the operations it may call, and this integration's document and discussion endpoints are read-only, so the agent only retrieves what you allow.
- **Credential handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### 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.