Promote the vendor names a catalogue sync has staged into suppliers
Promotes the vendor names an e-commerce catalogue sync has staged into real suppliers, and answers 200 with the plain body ok, not JSON, and not the {message, data} envelope. It takes no body and no parameters.
The rows it reads are written by the catalogue sync, so it has an effect only after a sync has run and only for vendors that are not suppliers yet. A vendor already on file is left exactly as it is, so running it twice is harmless and running it on a book with nothing staged is a no-op.
This is not a general import. import_suppliers is the door for a CSV of your own, and create_supplier for suppliers named in a request body.
Scope: suppliers:write, which includes suppliers:read.
Request
- Base URL: https://api.app.tightly.io
- URL: https://api.app.tightly.io/api/v1/inventory/suppliers/transfer-vendors
- Auth: HTTP bearer
Headers
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.
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.
Response
The staged vendors were promoted. The body is the two characters ok.
Changes
No recorded changes to this operation across all 1 revision of this API.