TransportOrders Ingestion
NxtPort operates a data sharing platform and uses the highest possible security standards to facilitate it's users. Data shared with NxtPort is stored in so-called data vaults that are specific for each customer separately. In order to store data in these vaults, each company needs to setup a connection to the NxtPort Ingestion Channels.
This document explains how to send data through to our Ingestion Channel.
Using JWT tokens
NxtPort uses Azure Active Directory B2C to provide business-to-customer identity as a service. It uses standards-based authentication protocols including OpenID Connect and OAuth 2.0.
Please refer to the article How to obtain an API Token for more information on the JWT token.
Setting up an https Ingestion Channel
Once you have successfully obtained a secured connection towards the NxtPort platform, you will receive a unique Ingestion Channel to store data into your vault on the platform. Such a channel is a unique URL which will look like https://[environment]/ingestion/[channel-id].
The environment will be depending on whether you are sending information to the live, UAT or testing environment and that for each environment the channel-id's are different.
If you are a third party service provider servicing multiple customers that (want to) share data with NxtPort International, each of these customers needs to have a separate ingestion channel setup to ensure the data storage follow our security foundations.
Posting information to your Ingestion channel
After receiving the Ingestion Channel endpoint and successfully obtaining a JWT token, you can send messages following the agreed messageType & mediaType via a POST method to the HTTPS endpoint.
In order to facilitate this, you can find a set of postman scripts attached to this article.
Environment settings
Ingestion collection
In order to use the environment script, you will need ID's from NxtPort. Please contact us should you not have received these or if you encounter issues while using them.
APIM API Ingestion - Prd.postman_environment.json APIM API Ingestion - Stg.postman_environment.json APIM API Ingestion.postman_collection.json