Release notes - Suppliers API
This page will show the changes made in the suppliers API version 2022v1. The changes are marked with a publish date to staging and production. New changes will be added at the top of the page.
W05 - AddSupplyLines order and delivery period
- Removed
TradePeriod
fromSupplyLineCreate
- Added
OrderPeriod
andDeliveryPeriod
intoSupplyLineCreate
published to staging: 3-2-2022
published to production: 3-2-2022
W05 - SupplyRequestLine IsLockedByCustomer
- Renamed property
IsPublishedByCustomer
fromSupplyRequestLine
intoIsLockedByCustomer
- Renamed endpoint
SetSupplyRequestLineIsPublishedByCustomer
intoSetSupplyRequestLineIsLockedByCustomer
published to staging: 3-2-2022
published to production: 3-2-2022
W05 - SupplyRequest order and delivery period
- Removed
TradePeriod
fromSupplyRequest
- Added
OrderPeriod
andDeliveryPeriod
intoSupplyRequest
published to staging: 3-2-2022
published to production: 3-2-2022
W05 - Stickers NumberOfCopies and NumberOfPages
- Renamed query parameter
duplicatePagesIfSingleLayout
inGetCustomerStickerById
intoduplicatePagesBasedOnNumberOfCopies
. - Removed property
quantity
. - Added property
numberOfCopies
. This property indicates how much copies must be printed of the pdf file. - Re-added property
numberOfPages
. This property now indicates how much pages there are in the pdf file.UploadLayout
SINGLE will always have 1 page.
published to staging: 01-02-2022
published to production: 01-02-2022
W05 - CustomerOffer Order- and DeliveryPeriod
Replaced TradePeriod
from CustomerOffer
with OrderPeriod
and DeliveryPeriod
.
The TradePeriod has been split into two different periods to indicate when the supply can be bought and when the supply will be delivered.
- Renamed model
CustomerOfferCreate
toAddCustomerOffer
- Renamed model
CustomerOfferUpdate
toEditCustomerOffer
published to staging: 01-02-2022
published to production: 01-02-2022
W04 - CustomPackage MaterialType
Added property MaterialType
to CustomPackage
.
published to staging: 27-1-2022
published to production: 27-1-2022
W04 - SyncResult
Changed all results from the sync endpoints (GetModelBySequenceNumber
) to a SyncResult<Model>
.
SyncResult contains a maximumSequenceNumber
based on the maximum sequence found before adding the optional post filter as used in the customers API and a list of results
with the Model type.
published to staging: 27-1-2022
published to production: 27-1-2022
W04 - OrderRequest
Added a new controller OrderRequests
for fetching and handling OrderRequest
.
An OrderRequest
always has a valid TradeItem and is placed without a supplyLine.
Accepting an OrderRequest
will result in a SalesOrder
without a SupplyLine
.
The supplier can specify in Floriday if the customers are allowed to post an OrderRequest
.
published to staging: 25-1-2022
published to production: 25-1-2022
W04 - SupplyLine counters
Added a new controller Counters
for fetching and handling Counters
.
Counter
can be used to add a stock countdown to your SupplyLine.numberOfPieces
.
You can create a new Counter
with an initialNumberOfPieces
and attach the counter to one or more SupplyLines
.
Whenever a SalesOrder
is created on a SupplyLine
with a Counter
, the numberOfPieces
of all the linked SupplyLines
will be changed with it.
You can only attach a Counter
to a SupplyLine
with type CATALOG_PRICE. The SupplyLine
must not be based on a BaseSupply and must not contain a Batch
.
The Counter
has a limit of maximum 200 SupplyLines
published to staging: 25-1-2022
published to production: 25-1-2022
W04 - Max sequence endpoint for FulfillmentOrder
Added GetFulfillmentOrdersMaxSequence
for syncing FulfillmentOrder
published to staging: 25-1-2022
published to production: 25-1-2022
W04 - Max sequence endpoint for DeliveryOrder
Added GetDeliveryOrdersMaxSequence
for syncing DeliveryOrder
published to staging: 25-1-2022
published to production: 25-1-2022
W04 - Max sequence endpoint for ClockPresalesSupplyLine
Added GetClockPresalesSupplyLinesMaxSequence
for syncing ClockPresalesSupplyLine
published to staging: 24-1-2022
published to production: 24-1-2022
W04 - Max sequence endpoint for ClockSupplyLine
Added GetClockSupplyLinesMaxSequence
for syncing ClockSupplyLine
published to staging: 24-1-2022
published to production: 24-1-2022
W03 - Remove Batch EditBaseSupply
Removed unused endpoint EditBaseSupply
based on batch.
published to staging: 19-1-2022
published to production: 19-1-2022
W03 - SupplyRequest endpoint routes
Changed name and route from SupplyRequest
endpoints:
- Changed
SetSupplyRequestAccepted
intoSetSupplyRequestLineAccepted
with routesupply-requests/line/{supplyRequestLineId}/accept
- Changed
SetSupplyRequestRejected
intoSetSupplyRequestLineRejectedForSupplierInternalAsync
with routesupply-requests/line/{supplyRequestLineId}/reject
published to staging: 19-1-2022
published to production: 19-1-2022
W03 - SalesOrderDelivery DeliveryCost
Added property DeliveryCost
to SalesOrderDelivery
.
DeliveryCost
indicates the re-calculated delivery cost based on the order amount in a specific delivery group with the same delivery time and location.
published to staging: 18-1-2022
published to production: 18-1-2022
W02 - CreateSalesOrder required packing configuration
Added model SalesOrderPackingConfigurationCreate
into SalesOrderRequest
with the following properties as required:
piecesPerPackage
packagesPerLayer
,layersPerLoadCarrier
package
LoadCarrierType
published to staging: 14-1-2022
published to production: 14-1-2022
W01 - SalesOrder invoice lines
Added GetInvoiceLinesBySalesOrderId
for fetching the financial invoice data.
- Property
deliveryFormReference
contains the delivery note - Property
SubTotalAmount
is the amount settled for the delivery note.
published to staging: 7-1-2022
published to production: 7-1-2022
W01 - StickerMetaData
Added and changed the properties of StickerMetaData
:
- Changed property
Sequence
from nullable long to long - Added property enum
StickerProvidedBy
. This property indicates who is responsible for providing the sticker. - Added property
DeliveryDateTime
. This property is the same as theLatestDeliveryDateTime
in theSalesOrder
- Added property
LastRequestedOn
. This property indicates the last time the pdf has been requested by the supplier. - Added property
StickerUploadLayout
. This property indicates wheter the pdf is uploaded with a single page which must be copied or a full pdf with multiple pages. - Added property
ParentId
. This property indicates which sticker meta data belong together.
published to staging: 6-1-2022
published to production: 6-1-2022
W01 - Sticker pdf by id
Added GetCustomerStickerById
for fetching the pdf of the sticker metadata.
The query parameter duplicatePagesIfSingleLayout
indicates if the pages of a single pdf must duplicated to the NumberOfPages
of the sticker metadata
published to staging: 6-1-2022
published to production: 6-1-2022
W01 - AddSalesOrder GLN required
Added the following models to use in SalesOrderRequest
- AddLocation
- AddSalesOrderDelivery
Removed property Address
and set property Gln
as required while creating a sales order.
published to staging: 3-1-2022
published to production: 3-1-2022
W01 - Contract payment provider
Added property PaymentProvider
to Contract
published to staging: 3-1-2022
published to production: 3-1-2022
W01 - CorrectionRequestStatus COMMITTED
Removed the following enum values from CorrectionRequestStatus
:
SALES_ORDER_CORRECTED
SALES_ORDER_CANCELLED
SALES_ORDER_CORRECTION_REJECTED
Added the following enum values to CorrectionRequestStatus
:
COMMITTED
COMMITTED
will be set after succesfully creating a new sales order version based on the correction request.
published to staging: 3-1-2022
published to production: 3-1-2022
W51 - SalesOrderCorrectionRequest IntendedForCustomerUser
Added property IntendedForCustomerUser
to SalesOrderCorrectionRequest
The user will be based on the Floriday account based on the first and last name.
published to staging: 23-12-2021
published to production: 23-12-2021
W51 - SalesOrderCorrectionRequest CreatedByUser
Added property CreatedByUser
to SalesOrderCorrectionRequest
The user will be based on the Floriday account based on the first and last name.
published to staging: 23-12-2021
published to production: 23-12-2021
W51 - Max sequence endpoint for Batch
Added GetBatchesMaxSequence
for syncing Batch
.
published to staging: 22-12-2021
published to production: 22-12-2021
W51 - SalesOrderCorrectionRequest sales order version
Added property SalesOrderVersionAfterCorrection
to SalesOrderCorrectionRequest
The correction will be updated with the new sales order version after the correction has been approved.
published to staging: 21-12-2021
published to production: 21-12-2021
W50 - Creating salesOrders with a minimum price
The Price
property in SalesOrderRequest
and SalesOrderExternalIntegrationRequest
has been replaced by AddPrice
with a minimum value of 0.001.
published to staging: 17-12-2021
published to production: 17-12-2021
W50 - Sync endpoint for TradeItemAvailability
Added GetTradeItemAvailabilitiesBySequenceNumber
and GetTradeItemAvailabilitiesMaxSequence
for syncing TradeItemAvailability
.
published to staging: 16-12-2021
published to production: 17-12-2021
W50 - SupplyRequest
You can now fetch SupplyRequests
and accept or reject SupplyRequestLines
. Accepting a SupplyRequestLine
will result in a new SupplyLine
of type CustomerOffer
.
published to staging: 16-12-2021
published to production: 17-12-2021
W50 - SalesOrder CreatedByUser
Added property createdByUser
to SalesOrderRequest
and SalesOrderExternalIntegrationRequest
.
You can enter the first and last name to indicate which Floriday user created the salesOrder.
The API will find the suppliers Floriday user based on the first and last name. The value will be set to null if no user has been found.
published to staging: 16-12-2021
published to production: 17-12-2021
W50 - DeliveryConditionId
Added property deliveryConditionId
to DeliveryCondition
published to staging: 16-12-2021
published to production: 17-12-2021
W50 - PackingConfigurationRequest
You can now fetch, accept or reject a PackingConfigurationRequest
When accepting a PackingConfigurationRequest
the tradeItem must contain the correct packing configuration available for the customer.
published to staging: 15-12-2021
published to production: 17-12-2021
W50 - TradeItemRequest
You can now fetch, accept or reject a TradeItemRequest
When accepting a TradeItemRequest
the chosen tradeItem must be available for the customer and must contain the correct packing configuration.
published to staging: 15-12-2021
published to production: 17-12-2021
W50 - SalesOrder credit check status
Added the property CreditCheckStatus
as nullable Enum to SalesOrder
The CreditCheckStatus
indicates whether the SalesOrder
has been accepted for payment by the payment service provider by checking and claiming the customer’s credit.
published to staging: 14-12-2021
published to production: 17-12-2021
W49 - SalesOrder correction requests
Endpoint ``
published to staging: 9-12-2021
published to production: 17-12-2021
W49 - AddBatchSupplyLineForSupplierInternal result code Accepted
Endpoint AddBatchSupplyLineForSupplierInternal
now returns status 202 Accepted when the Batch is currently unknown in the service. The SupplyLine will be created when the batch is processed.
published to staging: 8-12-2021
published to production: 17-12-2021
W49 - Renamed GetStickersById
Renamed endpoint GetStickersById
to GetTrayLabelsAsPdfById
published to staging: 7-12-2021
published to production: 17-12-2021
W47 - Get TradeItem by version
Added new endpoints for fetching a TradeItem by id and version GetTradeItemByIdAndVersion
published to staging: 24-11-2021
published to production: 17-12-2021
W46 - Max sequence endpoint for AdditionalService
Added GetAdditionalServicesMaxSequence
for syncing AdditionalService
.
published to staging: 18-11-2021
published to production: 18-11-2021
W43 - Endpoint naming conventions: Get
Naming conventions
- Include parameter names in function names for the
GetAttributes
.ById
shouldn't be used in POST, PUT, PATCH and DELETE. - Use clear denomination when using PATCH. For example
SetBlanketOrderApproved
instead ofSetBlanketOrderApprove
orApproveBlanketOrder
. - Avoid HTTP verbs in method names. So use
AddSalesOrder
instead ofPostSalesOrder
. The operation should define what it does, not which verb is used for it.HttpGet
, plural:GetAttributes
singular:GetAttribute
HttpPost
:AddAttribute
HttpPut
:EditAttribute
HttpPatch
:SetAttributeAvailable
andSetAttributeUnavailable
HttpDelete
:DeleteAttribute
Add consistency across all GET endpoints. Rename endpoint names to Get...
- ListSalesOrders renamed to GetSalesOrders
published to staging: 29-10-2021
published to production: 18-11-2021
W43 - Endpoint naming conventions: Put to Patch
Naming conventions
- Include parameter names in function names for the
GetAttributes
.ById
shouldn't be used in POST, PUT, PATCH and DELETE. - Use clear denomination when using PATCH. For example
SetBlanketOrderApproved
instead ofSetBlanketOrderApprove
orApproveBlanketOrder
. - Avoid HTTP verbs in method names. So use
AddSalesOrder
instead ofPostSalesOrder
. The operation should define what it does, not which verb is used for it.HttpGet
, plural:GetAttributes
singular:GetAttribute
HttpPost
:AddAttribute
HttpPut
:EditAttribute
HttpPatch
:SetAttributeAvailable
andSetAttributeUnavailable
HttpDelete
:DeleteAttribute
Add consistency across all PATCH endpoints. Changed some PUT endpoints to PATCH and rename endpoint names to Set...
- ApproveBlanketOrder renamed to SetBlanketOrderApproved and changed from PUT to PATCH
- CorrectFulfillmentOrders renamed to AddFulfillmentOrderCorrection and changed from PUT to PATCH
- DeactivateFlorecomOrderMessages renamed to SetFlorecomOrderMessagesDeactivated and changed from PUT to PATCH
published to staging: 29-10-2021
published to production: 18-11-2021
W43 - Sync endpoint for AdditionalService
Added GetAdditionalServicesBySequenceForSupplierInternal
for syncing AdditionalService
.
published to staging: 28-10-2021
published to production: 18-11-2021
W43 - Sync endpoint for CustomPackage
Added GetCustomPackagesBySequenceForSupplierInternal
and GetCustomPackagesMaxSequence
for syncing CustomPackage
.
published to staging: 28-10-2021
published to production: 18-11-2021
W43 - Sync endpoint for CommercialServiceType
Added GetCommercialServiceTypesBySequenceNumber
and GetCommercialServiceTypesMaxSequence
for syncing CommercialServiceType
.
published to staging: 28-10-2021
published to production: 18-11-2021
W43 - Endpoint naming conventions: Sync
Naming conventions
- Include parameter names in function names for the
GetAttributes
.ById
shouldn't be used in POST, PUT, PATCH and DELETE. - Use clear denomination when using PATCH. For example
SetBlanketOrderApproved
instead ofSetBlanketOrderApprove
orApproveBlanketOrder
. - Avoid HTTP verbs in method names. So use
AddSalesOrder
instead ofPostSalesOrder
. The operation should define what it does, not which verb is used for it.HttpGet
, plural:GetAttributes
singular:GetAttribute
HttpPost
:AddAttribute
HttpPut
:EditAttribute
HttpPatch
:SetAttributeAvailable
andSetAttributeUnavailable
HttpDelete
:DeleteAttribute
Add consistency across all GET sync endpoints. Rename endpoint names from GetChanged...Sync
to Get...BySequenceNumber
, changed sequence
to sequenceNumber
and changed the URLS from sync
to .../sync/{sequenceNumber}
- GetChangedClockSupplyLinesSync renamed to GetClockSupplyLinesBySequenceNumber
- GetChangedClockPresalesSupplyLinesSync renamed to GetClockPresalesSupplyLinesBySequenceNumber
- GetChangedBaseItemsSync renamed to GetBaseItemsBySequenceNumber
- GetChangedBatchesSync renamed to GetBatchesBySequenceNumber
- GetChangedBlanketOrdersSync renamed to GetBlanketOrdersBySequenceNumber
- GetChangedCollectionsSync renamed to GetCollectionsBySequenceNumber
- GetChangedConnectionsSync renamed to GetConnectionsBySequenceNumber
- GetChangedContractsSync renamed to GetContractsBySequenceNumber
- GetChangedCustomerStickerMetadata renamed to GetCustomerStickerMetadataBySequenceNumber
- GetChangedDeliveryConditionSetsSync renamed to GetDeliveryConditionSetsBySequenceNumber
- GetChangedDeliveryOrdersSync renamed to GetDeliveryOrdersBySequenceNumber
- GetChangedSupplyLinesSync renamed to GetSupplyLinesBySequenceNumber
- GetChangedFulfillmentOrdersSync renamed to GetFulfillmentOrdersBySequenceNumber
- GetChangedOrganizationsSync renamed to GetOrganizationsBySequenceNumber
- GetChangedSalesOrdersSync renamed to GetSalesOrdersBySequenceNumber
- GetChangedTradeItemsSync renamed to GetTradeItemsBySequenceNumber
- GetChangedWarehousesSync renamed to GetWarehousesBySequenceNumber
published to staging: 28-10-2021
published to production: 18-11-2021
W42 - Endpoint naming conventions: Put
Naming conventions
- Include parameter names in function names for the
GetAttributes
.ById
shouldn't be used in POST, PUT, PATCH and DELETE. - Use clear denomination when using PATCH. For example
SetBlanketOrderApproved
instead ofSetBlanketOrderApprove
orApproveBlanketOrder
. - Avoid HTTP verbs in method names. So use
AddSalesOrder
instead ofPostSalesOrder
. The operation should define what it does, not which verb is used for it.HttpGet
, plural:GetAttributes
singular:GetAttribute
HttpPost
:AddAttribute
HttpPut
:EditAttribute
HttpPatch
:SetAttributeAvailable
andSetAttributeUnavailable
HttpDelete
:DeleteAttribute
Add consistency across all PUT endpoints. Rename endpoint names from Put
to Edit
- PutBaseItem renamed to EditBaseItem
- PutBatches renamed to EditBatch
- PutWeeklySupplyLines renamed to EditWeeklySupplyLine
- PutWeeklyBaseSupply renamed to EditWeeklyBaseSupply
- PutContinuousStock renamed to EditContinuousStock
- PutTradeItemWarehouse renamed to SetTradeItemWarehouse
- PutCollection renamed to EditCollection
- PutCustomerOffers renamed to EditCustomerOffer
- PutCustomerStickersIsHandled renamed to SetCustomerStickersIsHandled
- PutSupplyLineStatus renamed to SetSupplyLineStatus
- PutBaseSupply renamed to EditBaseSupply
- PutFulfillmentOrders renamed to EditFulfillmentOrder
- PutSalesOrderCorrection renamed to EditSalesOrderCorrection
- PutTradeItem renamed to EditTradeItem
- PutTradeItemVariant renamed to EditTradeItemVariant
published to staging: 18-10-2021
published to production: 18-11-2021
W42 - Endpoint naming conventions: Post
Naming conventions
- Include parameter names in function names for the
GetAttributes
.ById
shouldn't be used in POST, PUT, PATCH and DELETE. - Use clear denomination when using PATCH. For example
SetBlanketOrderApproved
instead ofSetBlanketOrderApprove
orApproveBlanketOrder
. - Avoid HTTP verbs in method names. So use
AddSalesOrder
instead ofPostSalesOrder
. The operation should define what it does, not which verb is used for it.HttpGet
, plural:GetAttributes
singular:GetAttribute
HttpPost
:AddAttribute
HttpPut
:EditAttribute
HttpPatch
:SetAttributeAvailable
andSetAttributeUnavailable
HttpDelete
:DeleteAttribute
Add consistency across all POST endpoints. Rename endpoint names from Post
to Add
- PostBaseItem renamed to AddBaseItem
- PostBatches renamed to AddBatch
- PostBlanketOrder renamed to AddBlanketOrder
- PostWeeklySupplyLines renamed to AddWeeklySupplyLine
- PostCollection renamed to AddCollection
- PostCustomerOffers renamed to AddCustomerOffer
- PostDeliveryOrderGoodsMovement renamed to AddDeliveryOrderGoodsMovement
- PostDeliveryOrderAuction renamed to AddDeliveryOrderAuction
- PostSupplyLines renamed to AddSupplyLines
- PostFulfillmentOrder renamed to AddFulfillmentOrder
- PostImage renamed to AddImage
- PostSalesOrder renamed to AddSalesOrder
- PostSalesOrderExternalIntegration renamed to AddSalesOrderExternalIntegration
- PostTradeItem renamed to AddTradeItem
- PostTradeItemVariant renamed to AddTradeItemVariant
- PostWebhookSubscription renamed to AddWebhookSubscription
published to staging: 18-10-2021
published to production: 18-11-2021
W41 - Endpoint naming conventions: Patch
Naming conventions
- Include parameter names in function names for the
GetAttributes
.ById
shouldn't be used in POST, PUT, PATCH and DELETE. - Use clear denomination when using PATCH. For example
SetBlanketOrderApproved
instead ofSetBlanketOrderApprove
orApproveBlanketOrder
. - Avoid HTTP verbs in method names. So use
AddSalesOrder
instead ofPostSalesOrder
. The operation should define what it does, not which verb is used for it.HttpGet
, plural:GetAttributes
singular:GetAttribute
HttpPost
:AddAttribute
HttpPut
:EditAttribute
HttpPatch
:SetAttributeAvailable
andSetAttributeUnavailable
HttpDelete
:DeleteAttribute
Add consistency across all PATCH endpoints. Rename endpoint names to Set...
- PatchWeeklyBaseSupplyNumberOfPieces renamed to SetWeeklyBaseSupplyNumberOfPieces
published to staging: 15-10-2021
published to production: 18-11-2021
W41 - Endpoint naming conventions: Delete
Naming conventions
- Include parameter names in function names for the
GetAttributes
.ById
shouldn't be used in POST, PUT, PATCH and DELETE. - Use clear denomination when using PATCH. For example
SetBlanketOrderApproved
instead ofSetBlanketOrderApprove
orApproveBlanketOrder
. - Avoid HTTP verbs in method names. So use
AddSalesOrder
instead ofPostSalesOrder
. The operation should define what it does, not which verb is used for it.HttpGet
, plural:GetAttributes
singular:GetAttribute
HttpPost
:AddAttribute
HttpPut
:EditAttribute
HttpPatch
:SetAttributeAvailable
andSetAttributeUnavailable
HttpDelete
:DeleteAttribute
Add consistency across all DELETE endpoints. Rename endpoint names from Remove
to Delete
- RemoveTradeItemsFromCollection renamed to DeleteCollectionTradeItems
published to staging: 15-10-2021
published to production: 18-11-2021
W41 - Endpoint naming conventions: ById
Naming conventions
- Include parameter names in function names for the
GetAttributes
.ById
shouldn't be used in POST, PUT, PATCH and DELETE. - Use clear denomination when using PATCH. For example
SetBlanketOrderApproved
instead ofSetBlanketOrderApprove
orApproveBlanketOrder
. - Avoid HTTP verbs in method names. So use
AddSalesOrder
instead ofPostSalesOrder
. The operation should define what it does, not which verb is used for it.HttpGet
, plural:GetAttributes
singular:GetAttribute
HttpPost
:AddAttribute
HttpPut
:EditAttribute
HttpPatch
:SetAttributeAvailable
andSetAttributeUnavailable
HttpDelete
:DeleteAttribute
Add consistency across all endpoint names with an Id in the url parameter.
- GetAdditionalService renamed to GetAdditionalServiceById
- GetBaseItem renamed to GetBaseItemById
- GetBatch renamed to GetBatchById
- GetCollection renamed to GetCollectionById
- GetContractAttachment renamed to GetContractAttachmentById
- GetDeliveryConditionSet renamed to GetDeliveryConditionSetById
- GetDeliveryOrder renamed to GetDeliveryOrderById
- GetStickers renamed to GetStickersById
- GetSupplyLine renamed to GetSupplyLineById
- GetFulfillmentOrder renamed to GetFulfillmentOrderById
- GetFulfillmentOrderStatus renamed to GetFulfillmentOrderStatusById
- GetLogisticLabels renamed to GetLogisticLabelsById
- GetFulfillmentOrderCorrections renamed to GetFulfillmentOrderCorrectionsById
- GetSalesOrderCorrections renamed to GetSalesOrderCorrectionsById
- GetTradeItem renamed to GetTradeItemById
published to staging: 13-10-2021
published to production: 18-11-2021
W41 - Moved DirectSalesV2 endpoints to DirectSales
Renamed model SupplyLineCreateV2
into SupplyLineCreate
and moved the following endpoints to the DirectSales
tag:
- GetSupplyLinesMaxSequence
- PostSupplyLines
- PutSupplyLineStatus
- DeleteSupplyLine
published to staging: 13-10-2021
published to production: 18-11-2021
W39 - Removed the edit model in ApproveBlanketOrder
ApproveBlanketOrder no longer needs an edit model for approving the blanketOrder. You can use the newly added EditBlanketOrder if you want to edit the blanketOrder before approving.
published to staging: 29-09-2021
published to production: 18-11-2021
W39 - Added EditBlanketOrder endpoint
Added a new endpoint for editing a blanketOrder.
The edit model has been changed to allow for an incoterm
and contractLinePeriodId
.
published to staging: 29-09-2021
published to production: 18-11-2021
W39 - Straightened out sync endpoint names, description and parameters
Added missing limit parameter to GetChangedDeliveryConditionSetsSync and changed all sync endpoint operation names into GetChanged...Sync and added a default summary and description.
published to staging: 27-09-2021
published to production: 18-11-2021
W39 - Added GetMaxSequence endpoints
Added new endpoints /current-max-sequence
to fetch the maximum sequence available for the following models:
- BaseItem
- BlanketOrder
- Collection
- Connection
- Contract
- CustomerSticker
- DeliveryConditionSet
- SupplyLine
- Organization
- TradeItem
- Warehouse
published to staging: 27-09-2021
published to production: 18-11-2021
W38 - Removed the custom ErpProblemDetails and ErpValidationProblemDetails
Removed the temporary models ErpProblemDetails
and ErpValidationProblemDetails
and replaced them with the default ProblemDetails and ValidationProblemDetails.
published to staging: 23-09-2021
published to production:
W36 - Removed definition v1
Removed definition v1 from the swagger docs. You can only choose between the uuid or guid definitions.
published to staging: 10-09-2021
published to production: 18-11-2021
W36 - Cleaned up obsolete/not implemented endpoints and properties
- Removed endpoint GetAuctionStatus
- Removed endpoint GetClockSupplyLineById
- Removed endpoint GetPlantPassports
- Removed endpoint GetContracts
- Removed endpoint GetDeliveryOrders
- Removed endpoint PostSupplyLines
- Removed endpoint PutSupplyLineStatus
- Removed endpoint PatchSupplyLine
- Removed endpoint SyncSupplyExceptions
- Removed endpoint SyncSalesOrderFulfillmentSummaries
- Removed endpoint PatchOrganizationPaymentProviders
- Removed endpoint GetSalesChannel
- Removed property CarrierOrganizationId from BlanketOrderApprovalLine
- Removed property ExcludedCustomerOrganizationIds from SupplyLine
published to staging: 10-09-2021
published to production: 18-11-2021
Updated 5 months ago