suppliers

Detach many variants from one supplier, by id or by filter

Detaches many variants from one supplier and answers 204 with no body.

Name them as variant_ids in a JSON body, or as a comma-separated variant_ids query parameter. Both are read on every request and the two lists are added together, so send one or the other rather than the same ids twice.

filter_args and search in the body select by query instead, the way the variants table does, with exceptions naming the ids to keep. When either is sent, the explicit list is not used.

Defaults are repaired the way remove_variant_from_supplier repairs them: a variant left without a default supplier takes the first of the suppliers it still has. Prepacks are pruned in the same call and a prepack left holding one variant or none is deleted.

An unknown supplier is refused 404.

Scope: suppliers:write, which includes suppliers:read.

delete/api/v1/inventory/suppliers/{supplier_id}/variants

Request

  • Base URL: https://api.app.tightly.io
  • URL: https://api.app.tightly.io/api/v1/inventory/suppliers/{supplier_id}/variants
  • Auth: HTTP bearer

Path parameters

supplier_idstring required

The supplier's id, as list_suppliers serves it.

Query parameters

variant_idsstring
Example:var_88120,var_88121

Comma-separated variant ids, added to any variant_ids in the body. Omit it when the body carries the list.

Headers

Tightly-Versionstring
Example:2026-11

The date train to answer on. One train exists today, 2026-11, the one this reference describes and the one every key is minted on, so the call answers on it with or without this header. Send it anyway, so a client built now names its train from the start.

Idempotency-Keystring
Example:b8f1c0d2-6a4e-4f39-9c21-0d5f2e7a1b44

A string of your own, up to 255 characters, that makes this write safe to retry. Send the same key twice and the second request is answered with the first one's status and body instead of writing again, so a client that retried after a timeout ends holding the record's id rather than creating a second one. Reusing a key with a different body, or while the first request is still running, is refused 409. A write that failed releases its key. Keys answer for 24 hours and belong to the API key that used them. A key longer than 255 characters is ignored and the write goes ahead without the guarantee.

Request body

exceptionsstring[] nullable
searchstring nullable
variant_idsstring[]

Response

The pairs are gone. No body.

Changes

No recorded changes to this operation across all 1 revision of this API.