Driple Docs

Plans & Usage

Plan limits, usage tracking, and how to monitor your consumption.

Plans

PlanMonthly RequestsPriceBest for
Free1,000$0Testing & development
Starter50,000$29/moSmall stores, single app
Pro500,000$99/moGrowing businesses, multiple stores
Agency2,000,000$299/moAgencies, high-volume integrations

All plans include:

  • REST & GraphQL support
  • Automatic rate limit handling
  • Per-store bucket isolation
  • Structured request logging

Usage Tracking

Driple tracks your request count per calendar month (UTC). Every proxied response includes usage headers:

X-Driple-Usage: 4521
X-Driple-Limit: 50000

What counts as a request?

  • Each API call that is forwarded to Shopify counts as 1 request
  • Automatic retries (when Driple re-queues due to rate limits) also count
  • Failed authentication (401/403) does not count
  • Health check (/health) does not count

Monthly reset

Usage resets on the 1st of each month at 00:00 UTC.

Exceeding Your Limit

When you hit your plan limit, Driple returns:

HTTP/1.1 429 Too Many Requests

{
  "error": "plan_limit_exceeded",
  "message": "Monthly request limit of 1,000 reached for \"free\" plan.",
  "usage": 1000,
  "limit": 1000
}

Your existing Shopify access tokens continue to work — you can always fall back to calling Shopify directly (without rate limit protection) if needed.

Monitoring Usage

Via response headers

Check X-Driple-Usage and X-Driple-Limit on any proxied response.

Quick check script

curl -s -o /dev/null -w "Usage: %header{X-Driple-Usage} / %header{X-Driple-Limit}\n" \
  -H "X-Driple-Api-Key: drpl_xxx" \
  -H "X-Shopify-Access-Token: shpat_xxx" \
  "https://api.driple.dev/shopify/my-store/admin/api/2024-01/shop.json"

Upgrading

Visit driple.dev/pricing to upgrade your plan. Changes take effect immediately — no downtime, no request loss.

On this page