Restore a deleted subscription product

POSThttps://<your-url>/api/v2/subscription-products/{subscription_product}/actions/restore

MCP id subscription-products.actions.restore

Clears the soft-delete marker and returns the product in the detail view.

Token scope: api:write:subscription_products
Without it: 403 insufficient-token-scope.
Permission: subscription_products::create
Without it: 403 insufficient-permission.
Feature: Needs the billing feature on your organisation.
Without it: 404 endpoint-not-found.
Rate cost: 1 unit, write bucket. A write costs the same whatever view you ask for.
Also: Accepts Idempotency-Key. Accepts If-Match. Never cached: private, no-store. Unknown query parameters are refused, never ignored.

Both are checked, scope first. A token never does more than its user. How access is checked

Request

Example: Restore a deleted product

curl -X POST \
  'https://<your-url>/api/v2/subscription-products/1/actions/restore' \
  -H 'Authorization: Bearer <token>' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: <key>' \
  -d '{}'

const response = await fetch('https://<your-url>/api/v2/subscription-products/1/actions/restore', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer <token>',
    'Accept': 'application/json',
    'Content-Type': 'application/json',
    'Idempotency-Key': '<key>',
  },
  body: JSON.stringify({}),
});

use Illuminate\Support\Facades\Http;

$response = Http::withToken('<token>')
    ->acceptJson()
    ->withHeader('Idempotency-Key', '<key>')
    ->post('https://<your-url>/api/v2/subscription-products/1/actions/restore', [
    ]);

import requests
response = requests.request(
    'POST',
    'https://<your-url>/api/v2/subscription-products/1/actions/restore',
    headers={'Authorization': 'Bearer <token>', 'Accept': 'application/json', 'Content-Type': 'application/json', 'Idempotency-Key': '<key>'},
    json={},
)

Response

The shape of the response, with sample values.

{
  "data": {
    "id": 1,
    "name": "…",
    "description": "…",
    "purchase_price": "1250.00",
    "sales_price": "1250.00",
    "price_interval": "yearly",
    "is_hosting": false,
    "vat_rate": 1,
    "exact_item_id": "…",
    "exact_vat_code": "…",
    "exact_cost_center": "…",
    "created_at": "2026-03-04T09:15:00Z"
  },
  "meta": {
    "warnings": [
      {
        "…": "6 fields of warnings"
      }
    ]
  }
}

{
  "type": "https://developers.plnnrly.com/api/v2/problems/idempotency-key-in-flight",
  "title": "Idempotency key in flight",
  "status": 409,
  "detail": "The original request for this Idempotency-Key is still being processed. Retry shortly.",
  "instance": "/api/v2/worklogs",
  "request_id": "01K4B7Q9YV3PZ2N8T1E6M0XR4S"
}

{
  "type": "https://developers.plnnrly.com/api/v2/problems/precondition-failed",
  "title": "Precondition failed",
  "status": 412,
  "detail": "The record changed since the version named in If-Match. Re-read it and retry.",
  "instance": "/api/v2/work-items/812",
  "request_id": "01K4B7Q9YV3PZ2N8T1E6M0XR4S",
  "current_version": 12
}

3 more fields, listed under Response

Restoring additionally requires subscription_products::delete as well as subscription_products::create. Restoring a product that is not deleted succeeds and returns an already_in_target_state warning. The restore finds a deleted product on its own, so the trashed parameter is not accepted. This is also the remedy for a 422 unique on the name: the uniqueness check counts deleted products, so restoring the product that holds the name is the fix, not retrying under another one.

Path parameters

subscription_productintegerRequired

The SubscriptionProduct's numeric id. Accepts a soft-deleted record.

Query parameters

Unknown parameters are refused with 400, naming the parameter.

viewstring

Which field set to render.

summarydetaildefault

Request headers

X-Request-Idstringpattern

A correlation id of your own. It is recorded in our logs next to the server's request id but never returned: the response header always carries the server's id. A value that does not match the pattern is discarded silently, never rejected.

If-Matchstring

The ETag a write is conditional on. A stale validator is 412 precondition-failed.

Idempotency-Keystring≤ 255

A caller-chosen key that makes this POST safe to retry. Replaying it returns the original response with Idempotency-Replayed: true.

Response 200

Returns a SubscriptionProduct in the detail view.

Headers

ETag: A strong validator of exactly this representation.
Idempotency-Replayed: true when this response was replayed from a stored Idempotency-Key rather than produced by a new write.
RateLimit: The IETF httpapi-ratelimit-headers form of your remaining allowance on the tightest bucket this request touched.
RateLimit-Policy: The ceiling and window of that bucket, as <limit>;w=<seconds>.
X-Request-Id: The server-generated ULID correlating this response with our logs.

Every response also carries Cache-Control, Vary, X-Content-Type-Options, X-Plnnrly-Api-Version, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset. Headers and versioning