Admin Console

Your Control Center

Full control over your dedicated APIANT server. Account networks, connection sharing, rate limiting, deployment, monitoring, and user management. Manage everything. Even shut it down.

APIANT Editor Connections Dashboard Admin Console
CRMConnect: Master Account
Automations
User Activity
Work Queue
Webhooks
Error Log
System Keyvault
Connections
Account Network
Rate Limits
Deployment
System Usage
Admin Console [Main]: Automations
Search automations...
Filter
#NameStatusScheduleRunsErrors
4147 MindBody appointments → HubSpot deals v3.7 Active Every 10 min 12,847 0
4148 New class bookings → CRM contacts Active Instant (webhook) 8,421 2
4149 Membership renewals → HubSpot deals Active Every 15 min 3,209 0
4150 Client service depletion alerts Paused Every 1 hour 945 5
4151 HubSpot contact updates → MindBody Active Instant (webhook) 6,733 1
4152 Snowbird multi-location sync Active Every 30 min 2,156 0
228
Child accounts managed from one master
1
CRM connection shared across all locations
185
API calls per 10 seconds, enforced platform-wide
1-Click
Deploy upgrades to all accounts simultaneously

One Master. Hundreds of Child Accounts.

A master account with 228 child accounts, each representing a location. New locations get added to the network and immediately inherit shared connections and settings. This is how The Exercise Coach manages MindBody integrations across their entire franchise -- from a single control plane.

Scale Without Complexity

Each child account operates independently with its own source system connection (for example, its own MindBody site), but shares centrally managed resources like CRM connections and automation codebases.

When a franchise adds five new locations, those locations get added to the account network and immediately inherit shared connections, settings, and automations. No manual setup per location.
  Account Network
Master Account Locations 1 – 76 76 active Locations 77 – 152 76 active Locations 153 – 228 76 active 228 child accounts total

One Connection. Every Location.

The "Share with child account" toggle means one CRM connection shared across all locations. You do not need 228 separate CRM credentials. Each child account has its own source system connection (for example, its own MindBody site), but shares the CRM.

Shared Where It Matters. Isolated Where It Must Be.

Some connections need to be shared -- your CRM, your monitoring tools, your notification systems. Others must be isolated -- each location's source system credentials stay private to that child account.

The Admin Console gives you toggle-level control over what is shared and what is not. No code. No configuration files. Just a switch.

  Connection Sharing
ConnectionTypeShared
HubSpot CRM OAuth 2.0 SHARED
MindBody Site 1 API Key PRIVATE
MindBody Site 2 API Key PRIVATE
Slack Notifications OAuth 2.0 SHARED

Platform-Level Rate Limiting. No Code Required.

Set "185 API calls per 10 seconds" directly in the Admin Console. The platform enforces this across all 228 locations automatically -- no code, no external rate limiting tools, no per-location configuration.

Configured Once. Enforced Everywhere.

Rate limits are configured per connection at the platform level. Every automation, across every account in the network, respects the limit automatically. When an API partner tells you "185 calls per 10 seconds," you type that number once and the platform handles the rest.

The platform queues requests, distributes them evenly across the time window, and backs off gracefully when limits are approached. No 429 errors reaching your customers. No custom throttling code in your automations.
  Rate Limit Configuration
MindBody API: Rate Limit
185 API calls per 10 seconds
Current usage142 / 185 (77%)
Enforced across all 228 child accounts • Auto queue & backoff enabled

Master Account Routing

When data comes from the CRM and needs to go back to the correct source system, the master account dispatches to the proper child account. The platform handles routing automatically -- no manual mapping, no lookup tables, no guessing which location a record belongs to.

"A contact update comes into HubSpot. The master account receives the webhook, identifies which MindBody site the contact belongs to based on the location field, and routes the update to the correct child account. The child account processes it through its own automation with its own MindBody credentials. The contact never knows there are 228 locations behind the scenes."
  Master Account Routing: Webhook Dispatch
HubSpot CRM Webhook: Contact Update Master Account Route by Location ID location_field = "Site 47" Child: Site 12 MindBody credentials #12 Child: Site 47 MindBody credentials #47 Child: Site 203 MindBody credentials #203 Process Automation #4147

Deploy and Upgrade. All at Once.

One-Click Deployment to All Linked Accounts

Select the codebase group, deploy upgrades to all linked accounts simultaneously. No manual rollouts. No version drift. No missed locations.

When you fix a bug or add a feature, every customer gets it at the same time. The deployment workflow is built into the platform -- not bolted on as an afterthought.

Deployment is atomic. Either all accounts get the update, or none do. Rollback is one click away. You can also deploy to a subset of accounts for staged rollouts before going network-wide.
  Deployment
Deploy Codebase Group
MindBody → HubSpot CRM Suite v3.7
Target accounts: 228 of 228 selected
Current: v3.6 • Deploying: v3.7 6 automations affected
Deploy to All 228 Accounts

User Management and Access Control

Control who can access what across your entire APIANT server. Assign roles, manage permissions, and maintain security across your account network. Each team member sees only what they need to see.

👥

Role-Based Access

Assign roles to team members -- administrators, builders, viewers. Each role defines what actions a user can take and which accounts they can access within the network.

🔒

Account-Level Permissions

Grant access to specific child accounts without exposing the entire network. A regional manager sees their 30 locations. The master admin sees all 228.

🛠

Dedicated Server Control

This is your server. Full administrative control -- including the ability to shut it down. No shared infrastructure concerns. No noisy neighbors.

When Location 150 Says Something's Wrong, You Answer in Seconds

Supporting integrations at scale means answering questions fast. APIANT gives you complete visibility into every automation, every data flow, every API call. Search any piece of data -- a client ID, an email, a record number -- and instantly see every step it passed through, every transformation, every API response. No log diving. No guesswork.

Enterprise Monitoring Integration

For enterprise deployments, connect to Splunk, Datadog, or any monitoring tool for real-time dashboards showing API throughput, error rates, and rate limit compliance.

See exactly how many API calls per second are flowing through each connection, which automations are running, and whether any are approaching rate limits -- all in the monitoring tools your ops team already uses.

  Monitoring: API Throughput Dashboard
185 140 93 46 0 LIMIT: 185 12:00 12:30 13:00 13:30 14:00 API calls/10s Errors

Data Search and Inspection

Search any piece of data -- a client ID, a booking number, an email address -- and instantly see every step it passed through in the automation. See the raw API request, the transformation applied, and the final result written to the destination.

When a franchise location reports that a client's membership status did not sync correctly, you search the client ID and see the entire journey in seconds -- which automation processed it, what data came in, what decisions the branching logic made, and what was written to the CRM.
  Data Search: Client Journey
client_id: 8847291
Search
Found 4 steps for client_id: 8847291
Step 1: Trigger: New Booking Received
14:32:07 • MindBody webhook • 200 OK • 23ms
Step 2: Get Client Visits
14:32:07 • GET /client/8847291/visits • 200 OK • 145ms
Step 3: Branch: Custom Objects = YES
14:32:08 • Condition evaluated • True path taken
Step 4: Update HubSpot Custom Object
14:32:08 • PATCH /crm/v3/objects/appointments • 200 OK • 312ms

How the Admin Console Fits Into APIANT

The Assembly Editor creates ingredients. The Automation Editor builds recipes. The Admin Console deploys, monitors, and manages everything at scale.

Assembly Editor
Automation Editor
Admin Console
Production Deployment

Ready to Take Control?

See the Admin Console in action or explore the full platform.