Release notes - Customers API
This page will show the changes made in the customers 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.
W12 - PurchaseOrder ActionRequired
Added the following ActionRequired values:
- LOAD_CARRIER_DIFFERENCE
- PACKAGES_PER_LAYER_DIFFERENCE
- LAYERS_PER_LOAD_CARRIER_DIFFERENCE
published to staging: 21-3-2022
published to production: 24-3-2022
W07 - RequestStatus and SupplyRequestStatus
- Renamed enum value
ALL
fromRequestStatus
intoUNKNOWN
- Added new enum
SupplyRequestStatus
with an extra valueCOMMITTED
- Changed property
Status
fromSupplyRequestLine
from enumRequestStatus
intoSupplyRequestStatus
published to staging: 16-2-2022
published to production: 16-2-2022
W07 - AcceptSalesOrderCorrectionRequest and DeclineSalesOrderCorrectionRequest
Changed the body parameter from the endpoints from string
into SalesOrderCorrectionRequestAccept
and SalesOrderCorrectionRequestDecline
both with an optional string property.
published to staging: 16-2-2022
published to production: 16-2-2022
W06 - SalesOrderCorrectionRequest sync
- Changed property
Sequence
fromSalesOrderCorrectionRequest
intoSequenceNumber
- Changed the return value from endpoint
GetSalesOrderCorrectionRequestsBySequenceNumber
intoSyncResult<SalesOrderCorrectionRequest
published to staging: 10-2-2022
published to production: 10-2-2022
W06 - Sticker should be printed
Added the option ShouldBePrinted
in models AddSticker
, AddStickerFromSource
and Sticker
.
Floriday will validate the accepted upload layouts from the supplier when the sticker should be printed. Some suppliers only allow printed stickers with UploadLayout
SINGLE.
- Added property
IsDeleted
intoSticker
published to staging: 10-2-2022
published to production: 10-2-2022
W06 - SalesOrderCorrectionRequest
- Renamed model
SalesOrderCorrectionRequestCreate
intoAddSalesOrderCorrectionRequest
- Removed property
SupplierOrganizationId
from modelAddSalesOrderCorrectionRequest
- Renamed property
PackageTypeCode
from modelAddSalesOrderCorrectionRequest
andSalesOrderCorrectionRequest
intoVbnPackageTypeCode
and changed the type from nullable string into nullable int. - Changed the string length of property
Reason
from modelAddSalesOrderCorrectionRequest
to1000
- Added the string length
50
to propertyCreatedByUser
from from modelAddSalesOrderCorrectionRequest
- Added the string length
50
to propertyIntendedForSupplierUser
from from modelAddSalesOrderCorrectionRequest
published to staging: 10-2-2022
published to production: 10-2-2022
W05 - SelectedTradeItemPackingConfiguration endpoints
- Added endpoint
SetSelectedTradeItemPackingConfiguration
for adding newSelectedTradeItemPackingConfiguration
for a specificSelectedTradeItem
- Re-added
SetSelectedTradeItemPackingConfigurationPrimary
intoSelectedTradeItemsController
- Re-added
DeleteSelectedTradeItemPackingConfiguration
intoSelectedTradeItemsController
published to staging: 3-2-2022
published to production: 3-2-2022
W05 - SelectedTradeItemPackingConfigurations moved into SelectedTradeItem
Removed the SelectedPackingConfigurationsController and added SelectedPackingConfigurationTradeItem
into SelectedTradeItem
as property. An update in the selected packing configuration now results in a sequence bump of the selected trade item.
- Added property
SelectedPackingConfigurations
intoSelectedTradeItem
- Renamed property
LoadCarrierCode
intoLoadCarrierType
and changed the value to an enum. - Removed endpoint GetSelectedTradeItems. You can use
Removed the following redundant properties and endpoints from SelectedTradeItemPackingConfiguration:
- Removed property
SequenceNumber
fromSelectedTradeItemPackingConfiguration
- Removed property
SupplierOrganizationId
fromSelectedTradeItemPackingConfiguration
- Removed property
CustomerOrganizationId
fromSelectedTradeItemPackingConfiguration
- Removed property
TradeItemId
fromSelectedTradeItemPackingConfiguration
- Removed endpoint
GetSelectedTradeItemPackingConfigurationsBySequenceNumber
- Removed endpoint
GetSelectedTradeItemPackingConfigurationsMaxSequence
- Removed endpoint
AddSelectedTradeItemPackingConfiguration
published to staging: 3-2-2022
published to production: 3-2-2022
W05 - SelectedTradeItems new properties
Added the following properties into SelectedTradeItem
-
Added nullable property
CustomTradeItemName
intoSelectedTradeItem
-
Added nullable property
SelectedPhotoUrl
intoSelectedTradeItem
-
Added property
IsSelectedBySupplier
intoSelectedTradeItem
-
Added property
SelectedPackingConfigurations
intoSelectedTradeItem
-
Removed endpoint GetSelectedTradeItems. You can use the sync endpoint for fetching the
SelectedTradeItems
-
Renamed property
LoadCarrierCode
fromSelectedPackingConfiguration
intoLoadCarrierType
and changed the value to an enum.
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 optional PackingConfiguration
It is now possible to add a SupplyRequestLine without a PackingConfiguration
.
Added nullable property PackingConfiguration
into SupplyRequestLine
Removed the following properties from SupplyRequestLine
PiecesPerPackage
PackagesPerLayer
LayersPerLoadCarrier
VbnPackageCode
LoadCarrierType
published to staging: 3-2-2022
published to production: 3-2-2022
W05 - SupplyRequest order and delivery period
Removed TradePeriod
and added OrderPeriod
and DeliveryPeriod
in the SupplyRequest
and AddSupplyRequest
models.
published to staging: 3-2-2022
published to production: 3-2-2022
W05 - Sticker NumberOfCopies
The Quantity
property is no longer needed. You can now set the NumberOfCopies
while uploading a sticker.
NumberOfCopies
can also be set for UploadLayout
MULTIPLE. NumberOfPages
has been re-added and will be based of the uploaded pdf file and is no longer needed in AddSticker
.
- Renamed model
StickerRequest
intoAddSticker
- Renamed property
Quantity
fromAddSticker
intoNumberOfCopies
- Renamed model
StickerRequestFromSource
intoAddStickerFromSource
- Renamed property
Quantity
fromAddStickerFromSource
intoNumberOfCopies
- Re-added property
NumberOfPages
toSticker
- Added property
NumberOfCopies
toSticker
published to staging: 28-1-2022
published to production: 28-1-2022
W04 - DeliveryGroup
Added a new controller DeliveryGroups
. DeliveryGroups are an automatic enumeration of the sales orders with the same DeliveryDateTime
and delivery location. The DeliveryCost
in SalesOrder
will be recalculated based on this data.
published to staging: 28-1-2022
published to production: 28-1-2022
W04 - SupplyRequest nullable
It is now possible to create a SupplyRequest
without a PackingConfiguration
in the SupplyRequestLine
- Added nullable property
PackingConfiguration
toAddSupplyRequestLine
- Removed property
PiecesPerPackage
fromAddSupplyRequestLine
- Removed property
PackagesPerLayer
fromAddSupplyRequestLine
- Removed property
LayersPerLoadCarrier
fromAddSupplyRequestLine
- Removed property
VbnPackageCode
fromAddSupplyRequestLine
- Removed property
LoadCarrierType
fromAddSupplyRequestLine
published to staging: 28-1-2022
published to production: 28-1-2022
W04 - PurchaseOrder payment provider
- Added property
PaymentProvider
toAddPurchaseOrder
- Added property
PaymentProvider
toAddPurchaseOrderRequest
- Added property
PaymentProvider
toPurchaseOrder
published to staging: 28-1-2022
published to production: 28-1-2022
W04 - PurchaseOrder and OrderRequest
Added a new endpoint AddPurchaseOrderRequest
for creating a OrderRequest en removed the functionality in AddPurchaseOrder
.
- Renamed Model
PurchaseOrderRequest
intoAddPurchaseOrder
- Removed property
IsOrderRequest
fromAddPurchaseOrder
- Added Model
AddPurchaseOrderRequest
for the newAddPurchaseOrderRequest
endpoint
published to staging: 28-1-2022
published to production: 28-1-2022
W04 - Custom package details
- Added property
WeightInGram
toCustomPackage
- Added property
MaterialType
toCustomPackage
published to staging: 27-1-2022
published to production: 27-1-2022
W04 - Advance Shipping Notice (ASN)
Added a new controller AdvanceShippingNotices
and endpoints for fetching and handling incoming shipping.
It is now possible for buyers to retrieve deliveries from growers using an Advance Shipping Notice (ASN).
An Advance Shipping Notice is the delivery from a grower with information about which SalesOrder
is on which load carrier.
The information is similar to the DESADV but in contrast, can be retrieved when the grower makes his concept deliveries.
Because of the direct link with Floriday, the transport is more readily comprehensible. For the financial data there is a link to the SalesOrder
. If the buyer and the grower settle the corrections completely via Floriday, this is also immediately clear.
You can request the financial data on the basis of the linked SalesOrder
.
published to staging: 25-1-2022
published to production: 25-1-2022
W04 - SalesOrder payment provider
Added property PaymentProvider
to SalesOrder
published to staging: 24-1-2022
published to production: 24-1-2022
W04 - Max sequence endpoint for SalesOrder
Added GetSalesOrdersMaxSequence
for syncing SalesOrder
published to staging: 24-1-2022
published to production: 24-1-2022
W03 - AdditionalService Unit
Added property Unit
to AdditionalService
.
It will be possible for suppliers to set an Unit
for the AdditionalService
for the price calculation.
published to staging: 20-1-2022
published to production: 20-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
W03 - SupplyRequest is selected
Added endpoint SetSupplyRequestLineIsSelected
. Customers can select an approved SupplyRequestLine
. The supplier will not be able to change the price and number of pieces available in the SupplyLine
when the SupplyRequestLine
is set as selected.
published to staging: 18-1-2022
published to production: 18-1-2022
W02 - TradeItem IsHiddenInCatalog
Added property isHiddenInCatalog
to TradeItem
.
TradeItems that are hidden in the supplier catalog will now be returned in the sync and get endpoints and are no longer blocking while placing a sales order.
published to staging: 13-1-2022
published to production: 13-1-2022
W02 - PurchaseOrder endpoints and route changes
- Removed endpoint
GetPurchaseOrder
based oncustomerOrderReference
- Changed route for endpoint
GetPurchaseOrderById
frompurchase-orders/id/{purchaseOrderId}
topurchase-orders/{purchaseOrderId}
- Changed route for endpoint
DeletePurchaseOrder
frompurchase-orders/id/{purchaseOrderId}
topurchase-orders/{purchaseOrderId}
published to staging: 13-1-2022
published to production: 13-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 - SalesOrderCorrectionRequest
Added a new controller SalesOrderCorrectionRequest
and endpoints for fetching and handling the sales order corrections.
To make a correction on a sales order, you must first post a SalesOrderCorrectionRequest
.
The request must first be accepted by the supplier. The sales order will be corrected and a new version will be created after the request has been accepted.
It is also possible to accept or decline an correction request created by the supplier.
There can only be one open correction request per sales order.
published to staging: 7-1-2022
published to production: 7-1-2022
W01 - Sticker Quantity
Renamed property numberOfPages
into quantity
.
quantity
indicates how many pages the supplier must print.
- The quantity must be equal to the number of pages in the pdf in case of an
uploadLayout
of type MULTIPLE. - The quantity must be equal to the number of copies you wish to be printend in case of an
uploadLayout
of type SINGLE.
published to staging: 7-1-2022
published to production: 7-1-2022
W01 - Sticker ParentId
Added property parentId
to StickerRequest
and Sticker
.
You can now specify which stickers belong together.
published to staging: 7-1-2022
published to production: 7-1-2022
W01 - Sticker ProvidedBy
Added property stickerProvidedBy
to StickerRequest
and Sticker
.
You can now specify who will supply the stickers for the supplier.
published to staging: 6-1-2022
published to production: 6-1-2022
W01 - Sticker validation
It is now possible to upload stickers with a different quantity than indicated in the sales order.
Before the quantity had to be the same as the number of pieces or packages in the sales order.
With the new validation it is now possible to upload a pdf for only a specific part of the order.
published to staging: 6-1-2022
published to production: 6-1-2022
W01 - GetOrganizationsBySequenceNumber organizationType
Added optional query parameter organizationType
to GetOrganizationsBySequenceNumber
published to staging: 4-1-2022
published to production: 4-1-2022
W01 - Contract payment provider
Added property PaymentProvider
to Contract
published to staging: 3-1-2022
published to production: 3-1-2022
W51 - SupplyLine Unavailable
Set SupplyLine status as Unavailable when the numberOfPieces of pricePerPiece equals 0.
It is possible for the supplier to change the status back to available after increasing the price or numberOfPieces.
published to staging: 20-12-2021
published to production: 20-12-2021
W51 - CustomPackage deleted
Added property IsDeleted
to CustomPackage
published to staging: 20-12-2021
published to production: 20-12-2021
W50 - Renamed the parameters of the TradeItem and SupplyLine sync endpoints
Renamed the filter parameters of
GetTradeItemsBySequenceNumber and GetSupplyLinesBySequenceNumber.
GetTradeItemsBySequenceNumber
- Removed parameter
filterSelectedTradeItems
- Removed parameter
filterSelectedTradeItemPackingConfigurations
- Added parameter
postFilterSelectedTradeItems
with a default value oftrue
postFilterSelectedTradeItems
specifies whether only the tradeItems of the selectedtradeItems are to be returned.
- Added parameter
postFilterSelectedTradeItemPackingConfigurations
with a default value oftrue
postFilterSelectedTradeItemPackingConfigurations
specifies whether only the TradeItem.PackingConfiguration of the SelectedTradeItemPackingConfigurations are to be returned. Returns all the TradeItem.PackingConfigurations when there are no SelectedTradeItemPackingConfigurations found for the TradeItem.
GetSupplyLinesBySequenceNumber
- Removed parameter
includeUnselectedTradeItems
- Added parameter
postFilterSelectedTradeItems
with a default value oftrue
postFilterSelectedTradeItems
specifies whether only the supplyLines of the selectedtradeItems are to be returned.
published to staging: 17-12-2021
published to production: 17-12-2021
W50 - Removed SupplyLine.TradePeriod
Removed TradePeriod
from SupplyLine. The parameters OrderPeriod
and DeliveryPeriod
are used instead.
OrderPeriod
specifies the period during which you can place an order with the supplyLine.
DeliveryPeriod
specifies the period in which the order can be delivered to the customer.
published to staging: 14-12-2021
published to production: 17-12-2021
W50 - Added CreditCheckStatus to SalesOrder
Added CreditCheckStatus
to SalesOrder. The CreditCheckStatus
shows the customers credit status from RFH.
published to staging: 14-12-2021
published to production: 17-12-2021
W49 - GetPlantPassportDataBySalesOrderId
Added new endpoint for fetching SalesOrderPlantPassport by salesOrderId
published to staging: 8-12-2021
published to production: 17-12-2021
W49 - GetTradeItemsBySequenceNumber filter SelectedPackingConfiguration
Added a parameter to GetTradeItemsBySequenceNumber to add a filter to the tradeItem.PackingConfigurations to return only the selectedPackingConfigurations.
published to staging: 8-12-2021
published to production: 17-12-2021
W47 - Get TradeItem by id or version
Added new endpoints for fetching a TradeItem by id GetTradeItemById
or by id and version GetTradeItemByIdAndVersion
published to staging: 24-11-2021
published to production: 17-12-2021
W47 - PlantPassport model finetuning
- Renamed model
SalesOrderReferencePlantPassport
intoSalesOrderPlantPassport
. - Renamed property
SalesOrderRef
intoSalesChannelOrderId
- Added property
SalesOrderId
published to staging: 23-11-2021
published to production: 17-12-2021
W46 - PlantPassport data
Moved the plant passport data from the public API to the customers API. You can fetch plant passport information for a specific salesOrder.
published to staging: 15-11-2021
published to production: 17-11-2021
W45 - Added paymentsProviders to organization
Added the property PaymentProviders to OrganizationDetails
.
published to staging: 11-11-2021
published to production: 17-11-2021
W45 - Changed the supplier route to organization
Changed the suppliers/...
route to organizations/..
and removed endpoint GetSuppliers.
published to staging: 11-11-2021
published to production: 17-11-2021
W43 - Endpoint naming convenstions: 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...
and changed some PUT and POST to PATCH
- FinalizeBlanketOrder renamed to SetBlanketOrderFinalized and changed from PUT to PATCH
- ApproveBlanketOrder renamed to SetBlanketOrderApproved and changed from PUT to PATCH
- DeclineBlanketOrder renamed to SetBlanketOrderDeclined and changed from PUT to PATCH
- CancelSalesOrder renamed to SetSalesOrderCanceled and changed from POST to PATCH
published to staging: 29-10-2021
published to production: 17-11-2021
W43 - Sync endpoint for CustomPackage
Added GetCustomPackagesBySequenceNumber
and GetCustomPackagesMaxSequence
for syncing CustomPackage
.
published to staging: 28-10-2021
published to production: 17-11-2021
W43 - Sync endpoint for CommercialServiceType
Added GetCommercialServiceTypesBySequenceNumber
and GetCommercialServiceTypesMaxSequence
for syncing CommercialServiceType
.
published to staging: 28-10-2021
published to production: 17-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
- GetChangedAdditionalServicesSync renamed to GetAdditionalServicesBySequenceNumber
- GetChangedConnectionsSync renamed to GetConnectionsBySequenceNumber
- GetChangedContractsSync renamed to GetContractsBySequenceNumber
- GetChangedDeliveryConditionSetsSync renamed to GetDeliveryConditionSetsBySequenceNumber
- GetChangedPurchaseOrdersSync renamed to GetPurchaseOrdersBySequenceNumber
- GetChangedPackingConfigurationRequestsSync renamed to GetPackingConfigurationRequestsBySequenceNumber
- GetChangedSupplyRequestsSync renamed to GetSupplyRequestsBySequenceNumber
- GetChangedTradeItemRequestsSync renamed to GetTradeItemRequestsBySequenceNumber
- GetChangedSalesOrdersSync renamed to GetSalesOrdersBySequenceNumber
- GetChangedSelectedTradeItemSync renamed to GetSelectedTradeItemsBySequenceNumber
- GetChangedStickersSync renamed to GetStickersBySequenceNumber
- GetChangedOrganizationsSync renamed to GetOrganizationsBySequenceNumber
- GetChangedSupplyLinesSync renamed to GetSupplyLinesBySequenceNumber
- GetChangedTradeItemsSync renamed renamed to GetTradeItemsBySequenceNumber
- GetChangedWarehousesSync renamed renamed to GetWarehousesBySequenceNumber
published to staging: 28-10-2021
published to production: 17-11-2021
W42 - Selected trade item packing configuration
You can now select packing configurations from a specific trade item to follow. By setting a packing configuration as primary you can indicate a default packing configuration to show in Floriday as the default packing configuration when purchasing directly from Floriday. In the future it will be possible to also filter on selected trade item packing configurations while syncing the trade items.
published to staging: 22-10-2021
published to production: 17-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
- RemoveConnectionBySupplierOrganizationId renamed to DeleteConnection
- RemoveSelectedTradeItems renamed to DeleteSelectedTradeItems
- RemoveSelectedTradeItem renamed to DeleteSelectedTradeItem
published to staging: 15-10-2021
published to production: 17-11-2021
W41 - 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 Create
to Add
- CreateBlanketOrder renamed to AddBlanketOrder
- CreatePurchaseOrder renamed to AddPurchaseOrder
- CreatePackingConfigurationRequest renamed to AddPackingConfigurationRequest
- CreateTradeItemRequest renamed to AddTradeItemRequest
- CreateSupplyRequest renamed to AddSupplyRequest
- CreateSalesOrder renamed to AddSalesOrder
- CreateSticker renamed to AddSticker
- CreateStickerFromSource renamed to AddStickerFromSource
published to staging: 15-10-2021
published to production: 17-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.
- CreateConnection renamed to CreateConnectionBySupplierOrganizationId
- RemoveConnection renamed to RemoveConnectionBySupplierOrganizationId
- GetDeliveryConditionDetails renamed to GetDeliveryConditionDetailsById
- DeletePurchaseOrderById renamed to DeletePurchaseOrder
- CancelSalesOrderById renamed to CancelSalesOrder
- GetSalesOrderDeliveryNotes renamed to GetSalesOrderDeliveryNotesById
- GetStickerAsPdf renamed to GetStickerAsPdfById
- GetCertificatesOfSupplier renamed to GetCertificatesOfSupplierById
- GetDeliveryConditionSetOfSupplier renamed to GetDeliveryConditionSetOfSupplierById
- GetWarehousesOfSupplier renamed to GetWarehousesOfSupplierById
published to staging: 15-10-2021
published to production: 17-11-2021
W40 - Removed packingConfiguration from SupplyLine
Removed the obsolete property PackingConfiguration from supplyLine.
published to staging: 08-10-2021
published to production: 17-11-2021
W39 - Changed all enums to UPPER_SNAKE_CASE format
All enum values have been changed to an UPPER_SNAKE_CASE format.
published to staging: 29-09-2021
published to production: 29-11-2021
W39 - Set uuid definition as default format


Created a new definition UUID
that replaces the format guid
with uuid
in the swagger.json to be more in line with the Suppliers API.
published to staging: 28-09-2021
published to production: 29-11-2021
W39 - Added X-Api-Key header as security scheme


Added X-Api-Key as available authorization in the swagger page. You can now authorize the JWT Token and X-Api-Key for testing purpose on the swagger page.
published to staging: 28-09-2021
published to production: 29-11-2021
W39 - Added GetMaxSequence endpoints
Added new endpoints /current-max-sequence
to fetch the maximum sequence available for the following models:
- AdditionalService
- Connection
- Contract
- BlanketOrder
- DeliveryConditionSet
- PurchaseOrder
- TradeItemRequest
- PackingConfigurationRequest
- SupplyLineRequest
- SelectedTradeItem
- Sticker
- SupplyLine
- TradeItem
published to staging: 27-09-2021
published to production:
W38 - Removed X-Api-Key header parameter from endpoints
Removed the X-Api-Key
header parameter from the endpoints in order to be in line with the suppliers API. Every endpoint requires the X-Api-Key
in the header. You can set this as default in your own http client.
You can find more information about the API-key here.
published to staging: 22-09-2021
published to production: 29-11-2021
W37 - Cleaned up obsolete/not implemented endpoints and properties
- Removed endpoint GetContracts
- Removed endpoint GetContractsSync
- Removed endpoint DeletePurchaseOrder
- Removed endpoint GetPurchaseOrders
- Removed endpoint GetSupplierById
- Removed property CommercialServiceType from AdditionalService
- Removed property DeliveryCosts from DeliveryCondition
- Removed property Id from DeliveryConditionSetId
- Removed property DeliveryConditionId from PurchaseOrderDelivery
- Removed property BunchesPerPackage from SelectedPackingConfiguration
- Removed all v2 indications from endpoint names and routes
published to staging: 17-09-2021
published to production: 29-11-2021
W37 - Cleaned up sync endpoints
- Removed endpoint GetContractsSync and replaced it with GetChangedContractsSync
- Removed endpoint GetChangedBlanketOrdersSync and replaced it with GetChangedBlanketOrdersSyncV2
- Removed endpoint GetPurchaseOrdersSync and replaced it with GetChangedPurchaseOrdersSync
- Removed endpoint GetSalesOrdersSync and replaced it with GetChangedSalesOrdersSync
- Removed endpoint GetStickersBySequence and replaced it with GetChangedStickersSync
- Removed endpoint GetChangedOrganizationsSync and replaced it with GetChangedOrganizationsSyncV2
- Renamed endpoint GetSupplyLinesSync into GetChangedSupplyLines
- Removed property SupplyLines from SyncResultOfSupplyLine
- Removed property TradeItems from SyncResultOfTradeItem
published to staging: 17-09-2021
published to production: 29-11-2021
W37 - Replaced CreateSalesOrder with CreateSalesOrderV2
Replaced the old CreateSalesOrder endpoint with CreateSalesOrderV2 and removed the v2 from the endpoint name and path. CreateSalesOrder will always validate and return the errors as a bad request before creating a salesOrder.
Published to staging: 16-09-2021
published to production: 29-11-2021
Updated 3 months ago