Shared App Connections

Multi-location customers usually consolidate their data into a single vendor account — one HubSpot portal, one Stripe account, one Shopify store — even when they have many APIANT accounts (one per location). Sharing a single connection from the parent account across all of those linked child accounts avoids configuring the same credentials on every location and, more importantly, lets one connection-level rate-limit policy govern every child's traffic.

Why centralize the connection

• Rate limits. APIANT throttles each connection independently. One shared connection means every child account's traffic falls under a single throttle budget — the only way to keep N children from collectively blowing through the vendor's per-account rate limit.
• Config effort. One connection on the parent instead of configuring the same credentials on every child account.
• Credential rotation. When the vendor token rotates, you update one connection, not N.

Common cases

• A nation-wide multi-location operator (gym chains, franchise networks, healthcare systems) where every location feeds a single vendor account on the customer's side.
• Automation templates deployed to many linked child accounts that all need the same upstream connection.

Setting up a shared connection

Shared connections are configured in the UI rather than via the plugin. See:

• Sharing connections with linked child accounts
• Viewing shared connections