Faster time to market
Ship Pike13 workflows without building API plumbing.
Pike13 Connector
Embed Pike13 scheduling, client and staff workflows directly into your product. Build in-app automations to create or update client profiles, enroll clients into classes, sync staff schedules and surface Pike13 events per customer account.
Reduce support load
Automate bookings and client syncs to cut manual work.
Governed reuse
Expose vetted Pike13 actions as managed MCP tools.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
What you can integrate and automate with Pike13
Use the Pike13 connector to integrate and automate bookings, client and staff records, plans, visits, invoices and reporting queries across customer accounts. Cyclr lets product teams stitch Pike13 Core and Reporting APIs into reusable cycles, subscribe to Pike13 webhooks and publish those automations inside a white-label embedded marketplace. (developer.pike13.com)
PRODUCT USE CASES
Top Use Cases for Pike13 Integrations
Automate client onboarding, sync class enrollments and staff schedules, trigger notifications on check-ins and run scheduled reporting exports. Publish these automations into your product through Cyclr’s embedded integration marketplace for end users. (developer.pike13.com)
Create and sync client profiles
Automatically create Pike13 person records and sync profile updates between your app and Pike13 using Core API people endpoints. (developer.pike13.com)
Enroll clients and manage check-ins
Use Core API methods to enroll clients into plan products or event occurrences and trigger check-ins or attendance updates. (developer.pike13.com)
Webhook-driven notifications and actions
Subscribe to Pike13 Webhooks to receive visit, invoice or person events and drive in-app notifications or downstream automations. (developer.pike13.com)
ORCHESTRATION
How Pike13 works with Cyclr
Cyclr sits between your SaaS product and Pike13 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
Pike13
Pike13 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 Pike13 methods you can orchestrate through Cyclr.
Invoices2
Get Invoice
ActionGet an Invoices by ID.
List Invoices
ActionGet a List of All Invoice IDs.
Reporting - Clients1
List Clients
ActionList Clients (reporting)
Custom Fields1
List Custom Fields
ActionGet a List of Custom Fields associated with the Business.
People3
List People - Clients
ActionGet a List of All People.
List New People - Clients
ActionGet a List of All New People since last run time.
List Updated People - Clients
ActionGet a List of All Updated People since last run time.
TECHNICAL DETAILS
Pike13 integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing Pike13 integrations in Cyclr.
API and authentication
- API host
https://developer.pike13.com/docs/api/v2?utm_source=openai- Authentication
- OAuth 2.0
- Credentials
client_id, client_secret, redirect_uri; optional business subdomain selection.
- Method categories
Core CRUD (people, events, plans), Reporting queries, Webhooks, search and account endpoints.
Pagination and rate limits
Pagination
Offset pagination via page and per_page (default 20, max 100). Responses include total_count and prev/next links. (developer.pike13.com)
Rate limits
180 requests/min per access token; 360 requests/min per IP. RateLimit headers provide remaining and reset timestamps. (developer.pike13.com)
IMPLEMENTATION
Authentication at a glance
Authorization-code OAuth 2.0: register an app to obtain client_id and client_secret; access tokens used as Bearer header or access_token param and may be revoked. API access requires a registered app and Pike13 Premium plan. (developer.pike13.com)
- Authentication method
- OAuth 2.0
- Credential required
client_id, client_secret, redirect_uri; optional business subdomain selection.
Before you begin:
View setup guideAPI access requires Pike13 Premium plan and approved registered app. (developer.pike13.com)
COMMON QUESTIONS
Frequently asked questions
You can automate bookings, client and staff records, enrollments, check-ins, invoices and scheduled reporting exports. These actions map to Pike13 Core and Reporting APIs and webhook events. (developer.pike13.com)
OAuth 2.0 authorization-code is used: register a Pike13 app to get client_id and client_secret, exchange a code for an access token, then call APIs with Authorization: Bearer. Tokens may be scoped to business subdomains and can be revoked. (developer.pike13.com)
Yes. Cyclr supports per-tenant credentials and multi-tenant cycles so you can install the connector for each customer account and run tenant-scoped automations. Cyclr also lets you publish integrations to an embedded marketplace. (community.cyclr.com)
Yes. Cyclr lets you expose selected connector methods as managed, governed tools (MCP) for reuse and admin control, so product teams can safely recompose workflows. Governance and exposure happen in the Cyclr Console. (community.cyclr.com)
KEEP EXPLORING
Related resources and connectors
Documentation
HR Integrations to make your daily tasks easier
Read more →ProductCRM Integrations you should be using
Read more →ProductMCP PaaS
Read more →Related connectorBooker
Related Crms connector for customer-facing integration workflows.
Related connectorTan-Link
Related Crms connector for customer-facing integration workflows.
Related connectorAesthetic Record
Related Crms connector for customer-facing integration workflows.