Faster time to market
Ship customer integrations weeks faster.
Build in-app integrations that sync clients, patients, appointments, consultations, invoices and inventory between Provet Cloud and your SaaS. Use webhooks plus the REST API to surface real-time events and bulk sync historic records for multi-tenant customers.
Ship customer integrations weeks faster.
Author once, run across many tenants.
Expose only approved methods to customers.
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Use the Provet Cloud connector to sync and automate Provet records — clients, patients, appointments, consultations, invoices, stock items and related workflows — between Provet and your product. Provet exposes a REST API and webhook notifications; Cyclr orchestrates API calls, listens for webhooks and maps data across tenant accounts for embedded, customer-facing automations. (developers.provetcloud.com)
PRODUCT USE CASES
Automate operational workflows for multiple customer practices: sync clients and patients, create or update appointments and consultations, push invoices and reconcile stock levels across tenant Provet instances.
Create and update Provet client and patient records to keep CRM and support systems aligned using REST endpoints and webhook change notifications. (developers.provetcloud.com)
Create, update and cancel appointments or consultations in Provet from your app to streamline booking workflows and reduces double bookings. (developers.provetcloud.com)
Push invoices and reconcile payments between Provet and finance systems to automate billing and reporting. (developers.provetcloud.com)
ORCHESTRATION
Cyclr sits between your SaaS product and Provet Cloud to handle authentication, govern access and orchestrate every API call per customer, at scale.
Your app requests an action for a specific customer.
Cyclr authenticates, applies policies and routes the request.
Provet Cloud processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Explore Provet Cloud methods you can orchestrate through Cyclr.
Gets client list biased on partial match of email.
Gets updated clients since last run.
Create a new client.
Gets all clients.
Gets client by ID.
Gets new clients since last run.
Gets insurance claim client list.
Update a client.
Gets patient by ID.
Get New Patients.
Get Updated Patients.
Get Patients.
Create new patient.
Get Patients By Name.
Update Patient.
Gets unallocated payments for client.
Gets all unallocated payments.
Gets unallocated payments updated since last run.
Gets unallocated payments by ID.
Gets unallocated payments created since last run.
Create a new note.
Delete a phone number.
Update a phone number.
Gets list of species.
Gets list of breeds.
Gets invoices by ID.
Gets all invoices.
Gets all invoices for client.
Gets invoices created since last run datetime.
Gets invoices updated since last run datetime.
Gets invoice row by ID.
Gets updated invoice rows since last run.
Gets invoice rows by invoice ID.
Gets all invoice rows.
Gets new invoice rows since last run.
Gets list of invoice payments created since last run.
Gets list of invoice payments updated since last run.
Gets invoice payment by ID.
Gets all invoice payments for invoice.
TECHNICAL DETAILS
Review the sourced authentication and API behaviour used when configuring customer-facing Provet Cloud integrations in Cyclr.
https://provetcloud.com/client_id; client_secret; redirect_uri; provet_id (organization subdomain) or API token if enabled.
Read; Create; Update; Delete; Search; Webhooks; File uploads
List endpoints return up to 1,000 items per page and include next, previous, count and num_pages fields for traversal. (developers.provetcloud.com)
Endpoint-level rate limits apply; exceeding limits returns HTTP 429 with a Retry-After header. (developers.provetcloud.com)
IMPLEMENTATION
Provet documents OAuth 2.0 as the primary method (Authorization code with PKCE and Client Credentials). Legacy API tokens remain but are deprecated; confirm enabled options in Cyclr Console. (developers.provetcloud.com)
client_id; client_secret; redirect_uri; provet_id (organization subdomain) or API token if enabled.
Provet requires integration registration and approval before issuing OAuth credentials. (developers.provetcloud.com)
COMMON QUESTIONS
It synchronizes Provet records and events: clients, patients, appointments, consultations, invoices, stock items and webhook-triggered updates, enabling both real-time and bulk synchronizations. (developers.provetcloud.com)
OAuth 2.0 is the primary method — Authorization code with PKCE for user-facing apps and Client Credentials for server-to-server. Legacy API tokens exist but are deprecated. Provet issues client credentials after integration registration. (developers.provetcloud.com)
Yes. Cyclr orchestrates tenant-scoped connections: each customer uses their Provet instance (provet_id) and credentials so you can deploy the same workflow across multiple customer accounts. Provet requires approved applications per integration. (developers.provetcloud.com)
Yes. You can expose selected REST methods and webhook-driven actions as governed MCP tools with Cyclr, enforcing permissions, auditing and reusable orchestration at the product level.
KEEP EXPLORING
Related Miscellaneous connector for customer-facing integration workflows.
Related connectorRelated Miscellaneous connector for customer-facing integration workflows.
Related connectorRelated Miscellaneous connector for customer-facing integration workflows.