Faster time to market
Ship customer-facing PetExec automations in weeks.
PetExec Connector
Build in-app integrations that sync owners, employees and locations, create and update scheduled services and pull billing or statistics reports. Use Cyclr to surface PetExec data and actions inside your SaaS for booking automation, customer record sync and reporting workflows.
Scoped API access
Tokens use PetExec OAuth scopes for minimal permissions.
Reusable orchestration
Create one workflow and reuse across tenants.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Overview
Integrate PetExec to sync customer records, scheduled services (bookings), employee rosters, locations and billing or statistics reports. Cyclr lets you orchestrate PetExec API calls, map fields, schedule polling or on-demand actions, and expose those flows as white-label, in-app integrations linked to your tenant accounts. See the PetExec API documentation for endpoint details and scope requirements: PetExec API documentation.
PRODUCT USE CASES
Top use cases
Build multi-tenant automations that create or update owner records, mirror bookings, import employees and locations, and pull billing or report data for dashboards and reconciliation.
Create owner records in PetExec when users sign up
Automatically create or update owner (user card) records in PetExec from your app signups to keep contact and account data synchronized.
Mirror scheduled services and bookings
Create, update or cancel scheduled services in PetExec to reflect appointments booked inside your product, keeping calendars aligned.
Fetch billing and statistics reports
Pull PetExec billing and statistics reports for nightly reconciliation, dashboards and financial exports using the reports endpoints.
ORCHESTRATION
How PetExec works with Cyclr
Cyclr sits between your SaaS product and PetExec to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
PetExec
PetExec processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore PetExec methods you can orchestrate through Cyclr.
Scheduled Services3
List Service Types
ActionLists all scheduled service types.
List Services
ActionList all scheduled services by the specified type.
List Service Types & Services
ActionLists all scheduled service types and services.
Orders2
List New Orders
ActionRetrieves all orders since the last time this action was executed.
List Orders
ActionRetrieves all orders from the specified time range.
Owners1
Get Owner
ActionRetrieves the specified owner by User ID.
TECHNICAL DETAILS
PetExec integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing PetExec integrations in Cyclr.
API and authentication
- API host
https://secure.petexec.net/api- Authentication
- OAuth 2.0
- Credentials
Client ID; Client Secret; PetExec account name; Cyclr callback/redirect URL.
- Method categories
Owner/customer records; Scheduled services/bookings; Reports; Company (employees, locations); Preferences read/write.
Pagination and rate limits
Pagination
No published pagination spec. Many list endpoints return full JSON arrays; confirm pagination/query parameters in PetExec docs.
Rate limits
No numeric rate limits are published. Access is mainly bounded by requested OAuth2 scopes; confirm throttling with PetExec.
IMPLEMENTATION
Authentication at a glance
PetExec uses OAuth2 client credentials issued in the PetExec console (client_id and client_secret). Cyclr exchanges these via the OAuth token endpoint and requests scoped access (e.g. report_read, owner_read, scheduled_service_read).
- Authentication method
- OAuth 2.0
- Credential required
Client ID; Client Secret; PetExec account name; Cyclr callback/redirect URL.
Before you begin:
View setup guideRequires active PetExec account; set Cyclr callback URL and request required scopes.
COMMON QUESTIONS
Frequently asked questions
It syncs owner/customer records, scheduled services (bookings), employees, locations and billing/statistics reports. Cyclr workflows can create, update or fetch these PetExec objects to automate bookings, roster sync and reporting.
PetExec uses OAuth2: you create a Client ID and Client Secret in your PetExec account and set the Cyclr callback URL. Cyclr exchanges credentials for scoped bearer tokens (for example report_read, owner_read, scheduled_service_read).
Yes. Cyclr supports per-tenant OAuth credentials and reusable orchestration so you can embed white-label PetExec workflows across customer accounts while centralizing monitoring and updates.
Yes. Cyclr lets you expose connector methods as governed MCP tools or product features, so product teams can surface approved PetExec actions with centralized governance and version control.
KEEP EXPLORING
Related resources and connectors
Documentation
What is iPaaS?
Read more →ProductHow to develop an API – Best Practices to Follow from Cyclr Developers
Read more →ProductMCP PaaS
Read more →Related connectorOfficeR&D
Related Miscellaneous connector for customer-facing integration workflows.
Related connectorProvet Cloud
Related Miscellaneous connector for customer-facing integration workflows.
Related connectorRecruit CRM
Related Miscellaneous connector for customer-facing integration workflows.