Delete a template line

DELETEhttps://<your-url>/api/v2/subscription-type-items/{subscription_type_item}

MCP id subscription-type-items.destroyAlso on this path: GET Read a template line, PATCH Update a template line

Soft-deletes one template line.

Token scope: api:destroy:subscription_types
Without it: 403 insufficient-token-scope.
Permission: subscription_types::delete
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.
Also: 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: Remove a template line

curl -X DELETE \
  'https://<your-url>/api/v2/subscription-type-items/1' \
  -H 'Authorization: Bearer <token>' \
  -H 'Accept: application/json'

const response = await fetch('https://<your-url>/api/v2/subscription-type-items/1', {
  method: 'DELETE',
  headers: {
    'Authorization': 'Bearer <token>',
    'Accept': 'application/json',
  },
});

use Illuminate\Support\Facades\Http;

$response = Http::withToken('<token>')
    ->acceptJson()
    ->delete('https://<your-url>/api/v2/subscription-type-items/1');

import requests
response = requests.request(
    'DELETE',
    'https://<your-url>/api/v2/subscription-type-items/1',
    headers={'Authorization': 'Bearer <token>', 'Accept': 'application/json'},
)

Response

No body.

{
  "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
}

There is no permanent delete and no restore verb: a line comes back by being re-created through POST subscription-types/{subscription_type}/items, or by restoring the type it belonged to. Customer subscriptions already built from this template keep their own lines untouched (those were copied by value when the type was picked, not referenced), so deleting a template line changes nothing that is currently billing. Re-deleting an already-deleted line answers 204, so a retry is safe.

Path parameters

subscription_type_itemintegerRequired

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

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.

Response 204

Returns no content.

Headers

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