This guide covers everything you need to build a robust integration with Appstle Memberships. It includes authentication setup, the key endpoints for common workflows, and practical patterns for CRMs, email platforms, access control systems, and analytics tools.Documentation Index
Fetch the complete documentation index at: https://appstleinc-aeca3e0a.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Authentication
Merchant API key
For direct API access, pass the merchant’s API key in every request header:Direct API access requires an active API plan. Contact support@appstle.com for pricing.
Partner key
If you are building a product that integrates with Appstle Memberships — a CRM, helpdesk, email platform, or automation tool — you can apply for a Partner Key. Partner integrations bypass the paid plan requirement entirely.X-API-Key— The merchant’s API key, entered by the merchant in your integration settingsX-App-Key— Your partner key, provisioned by Appstle once during onboarding — the same key for all merchants using your integration
Base URL
/api/external/v2/.
Membership management
List membership contracts for a customer
Retrieve all membership contracts for a specific customer. This is the most common first call in any integration.Check membership status
Quickly verify whether a customer is an active member before granting access to gated content or applying member discounts:Get a specific contract
Retrieve full details for a single membership contract by its ID:List membership plans
Retrieve all membership plans available in a store:Billing operations
Cancel a membership
Cancel a customer’s membership programmatically:Pause a membership
Pause a membership contract:Resume a paused membership
Reactivate a membership that was previously paused:Common integration patterns
CRM / Helpdesk (Gorgias, Zendesk, HubSpot)
CRM / Helpdesk (Gorgias, Zendesk, HubSpot)
Help agents verify and manage memberships directly while handling support tickets:
- Look up member status by customer ID from the Shopify customer context
- Display active plan name, billing date, and contract status in the agent sidebar
- Cancel, pause, or update memberships directly from the helpdesk with a single API call
- Log actions back for audit trail purposes
GET /membership-contracts, GET /membership-status, POST /{contractId}/cancel, POST /{contractId}/pauseEmail / SMS Platform (Klaviyo, Omnisend)
Email / SMS Platform (Klaviyo, Omnisend)
Sync membership data for lifecycle automations:
- Use webhooks to receive real-time membership events (
membership.created,membership.cancelled, etc.) - Enrich customer profiles with membership tier, plan name, and next billing date
- Trigger flows based on events:
membership.billing-failure→ “Update your payment method” dunning sequencemembership.cancelled→ Win-back offer sequencemembership.created→ Welcome onboarding sequencemembership.expired→ Re-engagement campaign
GET /membership-contracts, webhook eventsAccess Control / Gated Content
Access Control / Gated Content
Control access to content, pages, or products based on active membership:
- On page load, call the membership status endpoint from your server-side code
- Check that
status === "ACTIVE"and that the plan grants access to the requested resource - Gate or unlock accordingly — redirect non-members to the plan selection page
- Cache membership status per session to stay within rate limits
GET /membership-status, GET /membership-contractsAnalytics / BI Tools
Analytics / BI Tools
Pull membership data for reporting and revenue projections:
- Use the membership contracts list endpoint with pagination to export all contracts
- Filter by
statusto track active vs. churned members - Use
nextBillingDateandbillingCycleTypefor MRR/ARR projections - Combine with webhook events to track churn in real time
GET /membership-contracts (paginated), GET /membership-plans, webhook eventsRate limits
API requests are rate-limited per store. If you receive a429 Too Many Requests response, implement exponential backoff before retrying. Cache membership status per customer session where possible to reduce the number of API calls.
Response format
All responses use standard HTTP status codes:| Status | Meaning |
|---|---|
200 | Success |
201 | Created |
400 | Bad Request — invalid parameters |
401 | Unauthorized — invalid or missing API key |
403 | Forbidden — key lacks permission |
404 | Not Found |
429 | Too Many Requests — rate limit exceeded |
500 | Server Error |
Resources
Webhooks
Receive real-time event notifications for membership lifecycle and billing events.
Shopify Flow
Automate membership workflows without writing code using Shopify Flow triggers.
Metafields & Tags
Shopify metafields and customer tags used for membership access control.