canonical: https://jentic.com/apis/swaggerhub.johnnywork/20-api-documentation

# Johnnywork 醫藥通 2.0 API Documentation

醫藥通 2.0 API Documentation. The API exposes 13 endpoints secured with bearer authentication.

## For AI agents

Programmatically 取得指定專案的基本設定 [1-1], 取得指定專案的註冊與同意書欄位設定 [1-7]. Covers 13 operations with bearer authentication.

## Scope

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

## Capabilities

- 取得指定專案的基本設定 [1-1]
- 取得指定專案的註冊與同意書欄位設定 [1-7]
- 取得指定專案的紀錄頁欄位設定 [1-8]
- 取得病患(自己)的贈藥紀錄 [8-1]
- HCP贈藥紀錄頁 - 病人清單頁籤 [8-2-3]
- HCP取得病患的贈藥紀錄 [8-3]
- 取得上傳記錄 [11-1]

## Use cases

### Developer Tools Operations

Use the 醫藥通 2.0 API Documentation to perform developer tools operations programmatically. The API provides 13 endpoints covering core functionality including 取得指定專案的基本設定 [1-1], 取得指定專案的註冊與同意書欄位設定 [1-7], 取得指定專案的紀錄頁欄位設定 [1-8].

Example prompt: Call GET `/config/project/{hash_id}` to 取得指定專案的基本設定 [1-1]

### Automated PAP 標準 Management

Automate pap 標準 operations by combining multiple 醫藥通 2.0 API Documentation endpoints. Agents can 取得指定專案的註冊與同意書欄位設定 [1-7] and then 取得指定專案的紀錄頁欄位設定 [1-8] in a single workflow.

Example prompt: Call GET `/v1/projects/{hash_id}/form-configs` to 取得指定專案的註冊與同意書欄位設定 [1-7], then verify the result

### AI Agent Integration via Jentic

AI agents discover and call 醫藥通 2.0 API Documentation 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 '取得指定專案的基本設定 [1-1]', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/config/project/{hash_id}` | 取得指定專案的基本設定 [1-1] |
| GET | `/v1/projects/{hash_id}/form-configs` | 取得指定專案的註冊與同意書欄位設定 [1-7] |
| GET | `/v1/projects/{hash_id}/record-configs` | 取得指定專案的紀錄頁欄位設定 [1-8] |
| GET | `/getPTMedicationRecord` | 取得病患(自己)的贈藥紀錄 [8-1] |
| GET | `/getHCPPatientList` | HCP贈藥紀錄頁 - 病人清單頁籤 [8-2-3] |
| GET | `/hcpGetPTMedicationRecord` | HCP取得病患的贈藥紀錄 [8-3] |
| GET | `/salesforce/upload-record` | 取得上傳記錄 [11-1] |
| POST | `/medicine/settings` | 儲存用藥提醒設定 |

## Key resources

- **PAP 標準** — Operations related to PAP 標準
- **提醒小幫手** — Operations related to 提醒小幫手

## Why Jentic

- **Setup:** Wiring the 醫藥通 2.0 API by hand means implementing its bearer token auth, pointing at the sandbox host, and writing your own retry handling around the project config, medication record, and appointment reminder calls. Through Jentic you install once, import the 醫藥通 2.0 API from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** This API puts the project id in the URL path (`/config/project/{hash_id}`, `/v1/projects/{hash_id}/...`), so a rule can pin your agent to one project and the operations around it. You choose the operations it may call, so writes like uploading a Salesforce record are not included unless you add them.
- **Credential handling:** Your 醫藥通 2.0 API 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 'get a project's form config' or 'fetch a patient medication record', and Jentic returns the matching 醫藥通 2.0 API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the 醫藥通 2.0 API Documentation use?

The 醫藥通 2.0 API Documentation 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 取得指定專案的基本設定 [1-1] with the 醫藥通 2.0 API Documentation?

Yes. Use the GET `/config/project/{hash_id}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the 醫藥通 2.0 API Documentation?

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 取得指定專案的基本設定 [1-1] through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for '取得指定專案的基本設定 [1-1]'. Jentic returns the matching 醫藥通 2.0 API Documentation operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the 醫藥通 2.0 API Documentation have?

The 醫藥通 2.0 API Documentation exposes 13 endpoints covering pap 標準, 提醒小幫手 operations.

### Can I limit what my agent is allowed to do with the 醫藥通 2.0 API?

Yes. Because you run Jentic One yourself, your own rules decide which 醫藥通 2.0 operations and which stored bearer token the agent may use. Since this API carries the project id in the URL path (`/config/project/{hash_id}`, `/v1/projects/{hash_id}/...`), a rule can pin the agent to a single project and only the read calls around it, such as GET `/config/project/{hash_id}` or GET /getPTMedicationRecord. You choose the operations it may call, so writes like POST `/medicine/settings` or `/salesforce/upload-record` stay off unless you add them.