Integrations & API Keys

    Manage API keys, configure webhooks, and connect third-party applications to GymPoint.

    Last updated: 05/21/2026

    Integrations & API Keys

    GymPoint provides an API and webhook system that lets you connect your gym's data with third-party tools, custom applications, and automation platforms. This guide covers how to generate API keys, set up webhooks, and use available integrations.

    Available Integrations

    GymPoint supports connections with a variety of external services. Navigate to Settings > Integrations to view and manage available integrations.

    Payment processing:

    • Poynt — primary payment processor for card payments, ACH, and terminal transactions

    Communication:

    • Email service provider for transactional and marketing emails
    • SMS provider for text message delivery

    Accounting:

    • Export-based integration with QuickBooks, Xero, and other accounting platforms via CSV exports and scheduled reports

    Marketing and automation:

    • Webhook-based connections to Zapier, Make (formerly Integromat), and similar platforms for custom automation workflows

    Each integration tile shows its connection status (Connected, Not Connected, or Error) and a Configure button. Active third-party connections are managed under Settings > Integrations > Connections.

    API Key Generation

    API keys allow external applications to authenticate with GymPoint's API on behalf of your organization.

    To generate an API key:

    1. Go to Settings > Integrations > API Keys.
    2. Click Generate New Key.
    3. Enter a label for the key (e.g., "Zapier Integration" or "Custom App").
    4. Select the permissions for the key:
      • Read Only — can retrieve data but cannot create, update, or delete
      • Read/Write — full access to create, update, and delete records
    5. Click Generate.
    6. Copy the API key immediately. It is displayed only once and cannot be retrieved later.

    API key security best practices:

    • Store API keys securely. Never expose them in client-side code or public repositories.
    • Use descriptive labels so you know what each key is used for.
    • Create separate keys for each integration rather than sharing one key across multiple services.
    • Rotate keys periodically by generating a new key and deactivating the old one.

    To revoke an API key:

    1. Go to Settings > Integrations > API Keys.
    2. Find the key in the list.
    3. Click Revoke.
    4. Confirm the action. The key stops working immediately.

    Webhook Configuration

    Webhooks let GymPoint push real-time event notifications to an external URL whenever something happens in your account.

    To set up a webhook:

    1. Go to Settings > Integrations > Webhooks.
    2. Click New Webhook.
    3. Enter the endpoint URL — the URL where GymPoint will send event data.
    4. Select the events you want to subscribe to:
      • member.created — a new member is added
      • member.updated — a member's profile is changed
      • member.deleted — a member is removed
      • membership.activated — a membership plan becomes active
      • membership.canceled — a membership is canceled
      • payment.successful — a payment processes successfully
      • payment.failed — a payment attempt fails
      • payment.refunded — a payment is refunded
      • checkin.created — a member checks in
    5. Optionally add a secret key for signature verification. GymPoint includes an HMAC signature in each webhook header so your endpoint can verify the request is authentic.
    6. Click Save.

    Testing webhooks:

    1. After creating a webhook, click Send Test to deliver a sample payload to your endpoint.
    2. Verify your endpoint received the request and responded with a 200 status code.
    3. If the test fails, check that your endpoint URL is correct and publicly accessible.

    Webhook retry behavior:

    If your endpoint returns a non-2xx status code or times out (30-second timeout), GymPoint retries the delivery:

    • 1st retry: 5 minutes after failure
    • 2nd retry: 30 minutes after failure
    • 3rd retry: 2 hours after failure

    After 3 failed retries, the event is logged as undeliverable. You can view failed deliveries under the webhook's activity log.

    Third-Party App Connections

    For platforms like Zapier or Make, use webhooks or API keys to create custom integrations.

    Example: Connecting to Zapier

    1. In Zapier, create a new Zap with a Webhook trigger.
    2. Copy the webhook URL from Zapier.
    3. In GymPoint, create a new webhook with that URL and select your desired events.
    4. In Zapier, configure the action (e.g., add a row to Google Sheets, send a Slack message, create a CRM contact).
    5. Test the Zap and turn it on.

    This approach lets you connect GymPoint to hundreds of apps without writing code.

    Tips

    • Start with webhooks if you want real-time notifications about events. They're simpler to set up than polling the API.
    • Use read-only API keys when possible. Only grant write access if the integration needs to modify data.
    • Monitor webhook activity regularly. Failed deliveries may indicate an issue with your receiving endpoint.
    • Document your integrations. Keep a record of which API keys and webhooks are active and what they connect to, so you can troubleshoot or clean up as needed.
    integrationsAPIwebhooksthird-partydeveloper