Delete an invoice line

DELETEhttps://<your-url>/api/v2/sales-invoice-rows/{sales_invoice_row}

MCP id sales-invoice-rows.destroyAlso on this path: GET Read an invoice line, PATCH Update an invoice line

Soft-deletes one line and recalculates the invoice's subtotal, vat_total and total in the same transaction.

Token scope: api:destroy:sales_invoices
Without it: 403 insufficient-token-scope.
Permission: sales_invoices::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 line

curl -X DELETE \
  'https://<your-url>/api/v2/sales-invoice-rows/1' \
  -H 'Authorization: Bearer <token>' \
  -H 'Accept: application/json'

const response = await fetch('https://<your-url>/api/v2/sales-invoice-rows/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/sales-invoice-rows/1');

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

Response

No body.

{
  "type": "https://developers.plnnrly.com/api/v2/problems/state-conflict",
  "title": "State conflict",
  "status": 409,
  "detail": "The target status is not reachable from this work item's current status.",
  "instance": "/api/v2/work-items/812/actions/transition",
  "request_id": "01K4B7Q9YV3PZ2N8T1E6M0XR4S",
  "conflict": {
    "reason": "illegal_transition",
    "from_workflow_status_id": 3,
    "to_workflow_status_id": 9
  }
}

{
  "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 sales-invoices/{sales_invoice}/rows, or by restoring the invoice it belonged to. Because this is a soft delete, worklogs settled against the line keep pointing at it: they are neither shown as re-invoiceable nor released, and re-creating the line does not re-couple them. Only deleting the whole invoice releases its hours. Re-deleting an already-deleted line answers 204, so a retry is safe. A line of a legacy or synced invoice answers 409 state-conflict. A caller without sales_invoices::finalize also returns the invoice to pending_approval, as editing the invoice itself does.

Path parameters

sales_invoice_rowintegerRequired

The SalesInvoiceRow'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