For Agents
Manage subscription orders, renewals, cancellations, and shipments for a Cratejoy subscription-box merchant. Use when an agent needs to drive subscription commerce lifecycle actions on Cratejoy.
Get started with Cratejoy API in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"cancel a cratejoy subscription"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Cratejoy API API.
Cancel, reactivate, skip, or renew a subscription via dedicated lifecycle endpoints
Add or remove coupons on an existing subscription
List, create, and update orders for a Cratejoy storefront
Track shipments associated with a subscription order
Manage customer shipping addresses and update them in place
GET STARTED
Use for: Cancel subscription 88241 effective at next renewal, Skip the next box for subscription 4421, Renew a past-due subscription so the customer keeps their box, Apply coupon 'WINTER10' to an active subscription
Not supported: Does not handle merchant signup, payment processor onboarding, or storefront theme editing — use for subscription, order, shipment, and webhook management only.
Cratejoy is a subscription commerce platform that lets brands run subscription-box businesses end to end, and the Cratejoy API exposes its merchant data and lifecycle controls. Across 32 endpoints, the API covers orders, subscriptions and their coupons and metadata, products, shipments, customer addresses, and outbound webhooks. Subscription-specific operations include cancel, reactivate, skip the next renewal, and renew a past-due subscription, which together cover the day-to-day churn and recovery actions a subscription merchant needs. Authentication is HTTP Basic with the merchant's API credentials.
Create outbound webhooks so external systems are notified on order or subscription events
Patterns agents use Cratejoy API API for, with concrete tasks.
★ Subscription Churn Recovery
When a customer's renewal fails because of an expired card, a churn-recovery workflow uses GET /v1/subscriptions/ to find past-due subscriptions and PUT /v1/subscriptions/{sub_id}/renew/ to retry once the customer updates their card. PUT /v1/subscriptions/{sub_id}/reactivate/ wins back customers who cancelled and changed their mind. This cuts involuntary churn without manual intervention.
Find past-due subscriptions via GET /v1/subscriptions/?state=past_due, then for each one PUT /v1/subscriptions/{sub_id}/renew/ and notify the customer of the result.
Skip-a-Box Self-Service
A subscriber decides to skip their next box because they are travelling. A self-service flow calls PUT /v1/subscriptions/{sub_id}/skip/ to skip the next renewal and PUT /v1/subscriptions/{sub_id}/skip/ again to unskip if plans change. This prevents cancellations driven by inflexibility while keeping the customer's plan intact.
PUT /v1/subscriptions/8821/skip/ to skip the next renewal for a holidaying customer, and confirm the response shows the next renewal pushed by one cycle.
Coupon and Promotion Application
Customer support applies a retention coupon to a subscriber thinking of cancelling. POST /v1/subscriptions/{sub_id}/coupons/ adds the coupon to the active subscription, and DELETE removes it later if the promo expires. GET /v1/subscriptions/{sub_id}/coupons/ confirms which coupons are currently applied so support sees the full picture.
POST /v1/subscriptions/{sub_id}/coupons/ with coupon code 'STAY20' for a churning customer, then GET /v1/subscriptions/{sub_id}/coupons/ to confirm the coupon is active.
Shipment and Address Operations
When a customer moves house, an automation updates their primary shipping address with PUT /v1/store/api/customer/addresses/{address_id}/ and confirms next month's shipment via GET /v1/store/api/shipments/. This avoids the box arriving at the wrong address and reduces support tickets.
PUT /v1/store/api/customer/addresses/{address_id}/ with the new street and postcode, then GET /v1/store/api/shipments/?subscription_id=8821 to confirm next month's box ships to the updated address.
Agent-Driven Subscription Concierge
An AI subscription concierge in a brand's support chat resolves common requests end to end: skipping a box, applying a retention coupon, updating shipping address, or renewing a past-due subscription. Through Jentic, the agent finds the right Cratejoy operation by intent and uses the merchant Basic auth credentials without holding them in plain text.
Search Jentic for 'skip a cratejoy subscription renewal', execute PUT /v1/subscriptions/{sub_id}/skip/, and reply to the customer that their next box has been deferred.
32 endpoints — cratejoy is a subscription commerce platform that lets brands run subscription-box businesses end to end, and the cratejoy api exposes its merchant data and lifecycle controls.
METHOD
PATH
DESCRIPTION
/v1/subscriptions/{sub_id}/cancel/
Cancel a subscription
/v1/subscriptions/{sub_id}/skip/
Skip or unskip the next renewal
/v1/subscriptions/{sub_id}/renew/
Renew a past-due subscription
/v1/subscriptions/{sub_id}/coupons/
Add a coupon to a subscription
/v1/orders/
List all orders
/v1/store/api/shipments/
List shipments
/v1/hooks/
Create an outbound webhook
/v1/subscriptions/{sub_id}/cancel/
Cancel a subscription
/v1/subscriptions/{sub_id}/skip/
Skip or unskip the next renewal
/v1/subscriptions/{sub_id}/renew/
Renew a past-due subscription
/v1/subscriptions/{sub_id}/coupons/
Add a coupon to a subscription
/v1/orders/
List all orders
Three things that make agents converge on Jentic-routed access.
Credential isolation
Cratejoy Basic auth credentials are stored encrypted in the Jentic vault. Jentic injects the Authorization header at execution time and rotates credentials when changed — agents never see them in plain text.
Intent-based discovery
Agents search Jentic with intents like 'cancel a cratejoy subscription' or 'skip the next box' and Jentic returns the matching Cratejoy operation with its input schema, drawn from the 32-endpoint spec.
Time to first call
Direct Cratejoy integration: 1-2 days for Basic auth setup, lifecycle endpoint coverage, and webhook signing. Through Jentic: under 1 hour — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
Shopify Admin API
Shopify is a general-purpose e-commerce platform with subscription apps available.
Choose Shopify when the merchant runs a broader catalogue and wants an app-based subscription bolt-on rather than a subscription-first platform.
Recharge API
Recharge is a subscription commerce platform that runs on top of Shopify and BigCommerce.
Choose Recharge when the merchant is already on Shopify and needs subscriptions layered onto their existing storefront.
Shopify Admin API
Some merchants run both a Cratejoy subscription store and a Shopify retail store and need to keep them in sync.
Use Shopify alongside Cratejoy when one-time merchandise lives in Shopify and the recurring subscription business lives in Cratejoy.
Specific to using Cratejoy API API through Jentic.
What authentication does the Cratejoy API use?
Cratejoy uses HTTP Basic authentication with the merchant's API credentials sent in the Authorization header. Through Jentic, the credentials are stored encrypted in the vault and added to outgoing requests at execution time.
Can I cancel a subscription through the Cratejoy API?
Yes. PUT /v1/subscriptions/{sub_id}/cancel/ cancels an active subscription. To bring it back, PUT /v1/subscriptions/{sub_id}/reactivate/ restarts billing at the next cycle.
How do I skip the next box for a subscriber through Jentic?
Search Jentic for 'skip cratejoy subscription renewal', load PUT /v1/subscriptions/{sub_id}/skip/, and execute with the subscription ID. Calling the same endpoint again unskips, which is useful if the customer changes their mind.
Can I apply a coupon to an existing subscription?
Yes. POST /v1/subscriptions/{sub_id}/coupons/ adds a coupon to an active subscription, and DELETE /v1/subscriptions/{sub_id}/coupon/{coupon_id}/ removes it. GET /v1/subscriptions/{sub_id}/coupons/ lists what is currently applied.
What are the rate limits for the Cratejoy API?
The OpenAPI spec does not declare numeric rate limits. Cratejoy enforces fair-use limits at the merchant level. Production integrations should retry on 429 responses with exponential backoff and avoid tight polling.
Does the Cratejoy API support webhooks?
Yes. POST /v1/hooks/ creates an outbound webhook subscription and PUT /v1/hooks/{hook_id}/ updates an existing one. Webhooks let external systems react to subscription and order events without polling.
/v1/store/api/shipments/
List shipments
/v1/hooks/
Create an outbound webhook