NEOM
On this page you will find information about selective DSV APIs dedicated for NEOM.
Get Started with Purchase Order management for NEOM - see the documentation, get access and test our NEOM API.
Download API Specification
Click here to download Open API json specification for NEOM.
Below you will find all operations possible to perform via NEOM API.
API: BPO Inbound
Submit purchase orders to DSV via the Orders APIs (click on each operation to see specification, then select "Group by tag")
Create or Update Order
Submit a purchase order to DSV or do changes to an already submitted order.Search Orders
Search for specific order based on the criteriaInsert eDoc
Add eDocs Meta Data to the Orders via APICancel Order
Delete submitted orders.
API: Bookings
Submit and handle a booking via the Booking APIs (click on each operation to see specification, then select "Group by tag")
Create or Update Booking(s)
Create new Bookings or update the existing oneRequest Booking Cancellation
Send cancellation request for your BookingInsert eDoc
Add eDocs Meta Data to the Booking via API
API: Delivery Orders
Submit and handle a booking via the Booking APIs (click on each operation to see specification, then select "Group by tag")
Create or Update Delivery Order(s)
Create new Delivery Order or update existing oneRequest Delivery Order Cancellation
Send cancellation request for your Delivery OrderInsert eDoc
Add eDocs Meta Data to the Delivery Order via API
Authorization
The available APIs are using a combination of two authentication methods to ensure a secure connection to DSV.
Authentication methods
API key (HTTP header: DSV-Subscription-Key)
This key is obtained by subscribing to the API via the above Subscribe link.
The key can be found in the DSV Developer portal profile page once the subscription request is approved by DSV.
2 keys are allocated per subscribed product, a “primary key” and a “secondary key”. Only one key (either primary key or secondary key) should be used in the HTTP header “DSV-Subscription-Key”.
Sample key structure: b5c09b92fbf24d62a17caad22227c470
System account (Authorization)
For security reasons, you will need to have an active account at DSV. When subscribing to the test API, a user email address and password will be provided by DSV to the EDC demo portal which must be used during tests.
The system account is using HTTP Basic authentication and all requests must contain the HTTP request header:
Authorization: Basic user-email:password
Support
If you have any questions please contact our Support team via email.