Skip to main content
This guide covers the main integration patterns for Appstle Bundles: reading merchant bundle configuration from a backend service and powering build-a-box flows on the storefront.

​
Base URL

All Bundles endpoints currently use this host:
Admin endpoints are prefixed with /api/external/. Storefront endpoints are documented in the generated Storefront API reference.

​
Authentication

Direct backend integrations pass the merchant’s API key in the X-API-Key header.
Keep this key server-side only.

​
Admin API endpoints

​
Get bundle rules

Retrieve configured bundle rules for a store.

​
Get discount rules

Retrieve discount-oriented bundle rules.

​
Get build-a-box rules

Retrieve build-a-box bundle rules.

​
Storefront API endpoints

Use the Storefront API reference for exact schemas. The main categories are:
Fetch build-a-box configuration by token, handle, or single-product context so a custom storefront can render the correct bundle experience.
Generate bundle discounts and shipping discounts for eligible build-a-box selections.
Ping visitor activity for Appstle storefront bundle widgets and customer-facing flows.

​
Production checklist

  • Keep Admin API keys server-side.
  • Cache bundle-rule reads where possible; merchant configuration changes less frequently than storefront traffic.
  • Treat Storefront API token parameters as flow-specific and avoid hard-coding them across shops.
  • Implement retries with exponential backoff for 429 and transient 5xx responses.
  • Log request IDs and response status codes for merchant-support debugging.