subscription-required
The merchant's Supliful membership no longer includes placing orders through the API.
subscription-required
HTTP 403. The key is valid and the account is active, but the merchant's Supliful membership does not include placing orders through the API. Only POST /v1/orders answers this way, and not for testMode orders, so the sandbox works without a membership.
{
"type": "https://developers.supliful.com/errors/subscription-required",
"title": "Subscription required",
"status": 403,
"detail": "This account's Supliful membership no longer includes placing orders through the API. A Pro or Enterprise membership is required.",
"instance": "/v1/orders"
}What it means
Placing orders through the API needs a Pro or Enterprise membership. The merchant's membership has lapsed or moved to a plan without it. The key and the connection are unchanged, which is why this answers 403 rather than invalid-api-key.
Everything except creating orders keeps working. You can still read products and orders, orders already placed are still fulfilled, and webhooks keep arriving for them. Resending a request that already placed an order, with the same idempotency key, still returns that order.
The membership is checked on every order, not when the key is issued. As soon as the merchant is back on Pro or Enterprise, the same key places orders again. You don't need a new key.
How to fix it
Your integration can't fix this. The membership has to be upgraded or renewed in the Supliful dashboard. Until then, hold new orders rather than dropping them.
Retry behaviour
Don't retry on a short interval. This lasts until the membership changes, which takes hours or days. Queue the orders and resend them once it has, using the same idempotency keys so nothing gets placed twice.