trama.

Archive a product

ARCHIVES the product: it leaves the active catalog and can be restored from the dashboard for 30 days, after which it is purged. Deliberately not an immediate delete — a buggy integration should not be able to destroy an agency's catalog.

DELETE
/v1/catalog/products/{productId}

ARCHIVES the product: it leaves the active catalog and can be restored from the dashboard for 30 days, after which it is purged. Deliberately not an immediate delete — a buggy integration should not be able to destroy an agency's catalog.

Authorization

AuthorizationBearer <token>

The organization API key, sent as Authorization: Bearer <key>.

In: header

Path Parameters

productId*string

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X DELETE "https://example.com/v1/catalog/products/string"
{  "archivedAt": "2019-08-24T14:15:22Z",  "id": "string"}

Update a product PATCH

Only touches the fields present in the body. Sending `null` clears a field; omitting it leaves it unchanged. Variants cannot be patched — send them on create, or the whole list would be replaced by a partial one.

Update a variant's declared availability PATCH

Declares how many spots are left on one variant, and whether it is on sale. Idempotent: send only what changed, repeat it as often as you like. The product can be addressed by Trama's id or by your own `externalReferenceCode`. 🔴 This is a DECLARATION, not a booking ledger. Trama never decrements it when a conversation closes, there are no holds and no overbooking checks — the number is whatever you last wrote. `inventoryUpdatedAt` is stamped by the server on every write; a `sold_out` or `closed` variant stops being quoted by the AI agent, and a remaining count stops being repeated once it goes stale.