canonical: https://jentic.com/apis/provetcloud.com/provetcloud

# Provet Cloud REST API

Provet Cloud's REST API offers most of the key Provet data to be read or manipulated by other systems. It provides access to veterinary practice management data including patients, clients, consultations, appointments, invoices, prescriptions, and online booking. The API exposes 30 endpoints secured with bearer, oauth2 authentication.

## For AI agents

Programmatically list clients, get a client. Covers 30 operations with bearer, oauth2 authentication.

## Scope

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

## Capabilities

- List clients
- Get a client
- Create a patient

## Use cases

### Healthcare Operations

Use the Provet Cloud REST API to perform healthcare operations programmatically. The API provides 30 endpoints covering core functionality including list clients, get a client, create a patient.

Example prompt: Call GET /client/ to list clients

### Automated Appointment Management

Automate appointment operations by combining multiple Provet Cloud REST API endpoints. Agents can get a client and then create a patient in a single workflow.

Example prompt: Call GET `/client/{clientId}`/ to get a client, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Provet Cloud REST 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, oauth2 tokens manually.

Example prompt: Search Jentic for 'list clients', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/client/` | List clients |
| GET | `/client/{clientId}/` | Get a client |
| POST | `/patient/` | Create a patient |
| GET | `/patient/` | List patients |
| GET | `/patient/{patientId}/` | Get a patient |
| GET | `/consultation/` | List consultations |
| GET | `/consultation/{consultationId}/` | Get a consultation |
| POST | `/appointment/` | Create an appointment |

## Key resources

- **Appointment** — Operations for appointment
- **Appointment_Reminder** — Operations for appointment_reminder
- **Client** — Operations for client
- **Consultation** — Operations for consultation
- **Consultationitem** — Operations for consultationitem

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 64 / 100
  - Developer Experience & Jentic Compatibility: 61 / 100
  - AI-Readiness & Agent Experience: 50 / 100
  - Agent Usability: 94 / 100
  - Security: 73 / 100
  - AI Discoverability: 82 / 100
- **View full report:** https://jentic.com/apis/provetcloud.com/provetcloud/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Provet Cloud REST API by hand means running its OAuth2 flow, keeping tokens fresh, and pinning requests to your own provetId host. Through Jentic you install once, import Provet Cloud from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Provet Cloud puts the resource id in the URL path (`/patient/{patientId}`/, `/client/{clientId}`/, `/consultation/{consultationId}`/), so a rule can pin your agent to reading a specific patient or client. You choose the operations it may call, so writes like creating a patient or appointment are not included unless you add them.
- **Credential handling:** Your Provet Cloud REST API credential 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 'list clients' or 'read a patient record', and Jentic returns the matching Provet Cloud operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Oystehr** — Alternative healthcare API
- **Athenahealth** — Alternative healthcare API

## FAQ

### What authentication does the Provet Cloud REST API use?

The Provet Cloud REST API uses bearer, oauth2 authentication. 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 list clients with the Provet Cloud REST API?

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

### What are the rate limits for the Provet Cloud REST 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 list clients through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list clients'. Jentic returns the matching Provet Cloud REST API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Provet Cloud REST API have?

The Provet Cloud REST API exposes 30 endpoints covering appointment, appointment_reminder, client operations.

### Can I limit what my agent is allowed to do with the Provet Cloud REST API?

Yes. Jentic One runs self-hosted, so your own rules decide which Provet Cloud operations and credentials your agent may use. Because Provet Cloud puts the resource id in the URL path, such as `/patient/{patientId}`/, `/client/{clientId}`/, and `/consultation/{consultationId}`/, you can pin the agent to reading a specific patient, client, or consultation. You also choose the operations it may call, so writes like creating a patient or an appointment are excluded unless you add them.