Retrieve the queued charge you want to skip with GET /charges?subscription_id=SUBSCRIPTION_ID&status=queued to obtain the charge_id
Skip the charge with POST /charges/CHARGE_ID/skip — this marks the charge as skipped and moves next_charge_scheduled_at to the following billing date
Optionally unskip with POST /charges/CHARGE_ID/unskip if the skip was applied in error before the charge processes
Confirm the subscription's updated next_charge_scheduled_at with GET /subscriptions/SUBSCRIPTION_ID
Webhook subscription/charge_skipped fires after a successful skip — register it via POST /webhooks to notify downstream systems
Known gotchas
You can only skip a charge that has status queued; attempting to skip a charge with status success or error returns a 422 error
Skipping a charge does not create a compensating order or credit — the customer simply does not receive a shipment for that cycle
If a subscription has charge_interval_frequency different from order_interval_frequency (prepaid plans), skipping one charge may skip multiple order cycles
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp