Provet Cloud REST API

Name: Provet Cloud REST API
Brand: Provet Cloud REST API
Availability: InStock

✓ Official Vendor SpecHealthcareAppointment Schedulingbearer, oauth230 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Provet Cloud REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Provet Cloud REST 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 Provet Cloud REST API.

List clients

Get a client

Create a patient

Use Cases

GET STARTED

Start building with Provet Cloud REST API

Explore with Jentic

View OpenAPI Document

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.

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.

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

Key Endpoints

30 endpoints — provet cloud's rest api offers most of the key provet data to be read or manipulated by other systems.

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

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

Why Jentic?

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

Credential isolation

Provet Cloud REST API bearer, oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'list clients') and Jentic returns the matching Provet Cloud REST API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Provet Cloud REST API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Provet Cloud REST API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.

Provet Cloud REST API

Connect the Provet Cloud REST API to your agent

Capabilities

Use Cases

Start building with Provet Cloud REST API

Key Endpoints

Why Jentic?

Related APIs

FAQs