Skip to main content

· 4 min read

Teaser image
Photo by Jaye Haych on Unsplash

General notes about application API keys

Application API keys provide our customers with access to their data in an unsupervised setting, and is specifically intended for use with machine to machine communication. It is recommended to use application API keys rather than user sessions for applications and scripts that require access to our APIs. This makes it possible to avoid sharing your credentials with applications, scripts or unsupervised machines.

· 5 min read

Teaser image
Photo by Tony Stoddard on Unsplash

In an increasingly connected world our customers need operational data about their vessels at their fingertips in order to make well-informed and clear decisions. This poses the immediate question of how to securely transmit data from the ship to the shore side. For most of the history in seafaring, vessels have been independent and totally isolated environments. This, however, is no longer the case. By connecting the vessel to the outside world, new risks and challenges have arisen. How do we do this while providing peace of mind? This is where our Ship-to-Shore solution comes into play. We provide simple and safe data transmission technology following highest security standards such as the European General Data Protection Regulation (GDPR).

· 8 min read

Teaser image
Photo by Med Badr Chemmaoui on Unsplash

You've just built an awesome API as a product and want your customers to easily understand and explore its features? This will certainly make you wonder how you could best provide documentation about this API to your customers.

On first publication of our ship-data and analytics APIs we hit this question as well. After a quick research about available solutions we opted - due to a lack of other options - for the official AWS API Gateway Developer Portal.

Fast-forward: Not only did we have a hard time customizing the portal but AWS informed us about a severe security issue inside the portal which would force us to migrate to a newer version. Migration, however, was such a nasty experience, that we took this as a reason to search for better and easier maintainable solutions.

This was the trigger for coming up with our current solution. A stupid simple and yet fully serverless portal to document your public facing APIs - and all of this beautifully. Check it out at