A transfer note in Flexi always has two sides — an issue from the source warehouse and a receipt at the destination. Via the API, it is therefore created in two steps, which can, however, be part of a single request.
1. Issue note for the transfer
<winstrom version="1.0">
<skladovy-pohyb>
<id>code:PREVOD1</id>
<typDokl>code:STANDARD</typDokl>
<typPohybuK>typPohybu.vydej</typPohybuK>
<typPohybuSkladK>typPohybuSklad.vydejPrevod</typPohybuSkladK>
<sklad>code:PLZEN</sklad>
<skladCil>code:PLZ</skladCil>
<skladovePolozky>
<skladovy-pohyb-polozka>
<cenik>code:1040CM</cenik>
<sklad>code:PLZEN</sklad>
<typPolozkyK>typPolozky.katalog</typPolozkyK>
<mnozMj>1</mnozMj>
</skladovy-pohyb-polozka>
</skladovePolozky>
</skladovy-pohyb>
</winstrom>
Two elements are key here: typPohybuSkladK with the value typPohybuSklad.vydejPrevod and skladCil with the destination warehouse.
2. Completing the transfer
Call the action on the created issue note, which automatically creates a linked receipt note at the destination warehouse:
<winstrom version="1.0">
<skladovy-pohyb action="dokoncit-prevodku">
<id>code:PREVOD1</id>
</skladovy-pohyb>
</winstrom>
The resulting receipt note is linked to the issue note via the typVazbyDokl.hlavaSklPrevod relation, so you can look it up through the vazby relation. Instead of the code, you can also use the internal number of the transfer issue note as the identifier.
💡 Both steps can be part of a single request — simply place both skladovy-pohyb elements one after another, with the second one carrying the action="dokoncit-prevodku" attribute. The import will process them in the order in which they are listed.