> ## Documentation Index
> Fetch the complete documentation index at: https://developers.perkstar.co.uk/llms.txt
> Use this file to discover all available pages before exploring further.

# Integration gallery

> Choose a supported connection or build a reliable custom integration with Perkstar's public platform.

Perkstar supports direct connections for common business systems and a public
developer platform for bespoke POS, ERP, CRM, and commerce workflows.

## Available in the dashboard

<CardGroup cols={2}>
  <Card title="Square" icon="square">
    Connect locations and customers, ingest eligible sales and refunds, and keep
    loyalty activity linked to the Square merchant.
  </Card>

  <Card title="Shopify" icon="shopify">
    Connect a store, map locations and loyalty cards, and reconcile eligible
    orders, edits, refunds, and customer identities.
  </Card>

  <Card title="Acuity Scheduling" icon="calendar-check">
    Connect appointment activity to loyalty and configure the card and reward
    journey used for attended bookings.
  </Card>

  <Card title="Klaviyo" icon="envelope">
    Sync consented customer profiles and selected loyalty activity into Klaviyo
    for lifecycle messaging.
  </Card>

  <Card title="Stripe" icon="stripe">
    Perkstar's payment connection for paid cards, memberships, gifts,
    multipasses, and tickets.
  </Card>
</CardGroup>

Availability can depend on the business plan, provider region, account
capabilities, and Perkstar configuration. The dashboard is authoritative for
what a particular business can connect.

## Controlled rollout

<CardGroup cols={2}>
  <Card title="Clover" icon="cash-register">
    OAuth connection, scan-first POS redemption, paid-order finalisation,
    refunds, and reconciliation are in controlled rollout.
  </Card>

  <Card title="Loyverse" icon="store">
    OAuth sales and refund sync, multi-location mapping, and customer matching
    are in controlled rollout.
  </Card>
</CardGroup>

Controlled-rollout integrations are enabled with Perkstar support after a
merchant and regional compatibility check. They should not be promised as
self-serve until they appear as available in that business's dashboard.

## Build your own

<CardGroup cols={3}>
  <Card title="Direct API" icon="key" href="/quickstart">
    Use a business API key for one merchant, one Odoo database, or an internal
    service.
  </Card>

  <Card title="Marketplace OAuth" icon="users" href="/guides/oauth-marketplace">
    Let many businesses install the same application with scoped consent and
    rotating tokens.
  </Card>

  <Card title="POS walkthrough" icon="cash-register" href="/guides/pos">
    Follow the end-to-end till flow for identity, earning, reversal, retry, and
    reconciliation.
  </Card>

  <Card title="Webhooks" icon="webhook" href="/reference/webhook-events">
    Receive signed customer, loyalty, commerce, membership, and booking events.
  </Card>

  <Card title="Postman" icon="paper-plane" href="/tools/postman">
    Import the generated collection and test all public v1 operations.
  </Card>

  <Card title="MCP" icon="sparkles" href="/tools/mcp">
    Connect an AI client to read-only business reporting with OAuth consent.
  </Card>
</CardGroup>

Check the [API availability matrix](/support/api-availability) before designing
against rewards, vouchers, tiers, or orders. It distinguishes stable public
resources from workflows that are currently available only through the
dashboard, events, or provider-specific integrations.


## Related topics

- [Integration gallery](/integrations/index.md)
- [Build a POS integration](/guides/pos.md)
- [Build an OAuth marketplace app](/guides/oauth-marketplace.md)
- [Connect Odoo](/guides/odoo.md)
- [Synchronise customers](/guides/customer-sync.md)