Public API

The Maritech Public API is a REST API for connecting external systems to Maritech Cloud
​

It's a shared integration layer across all applications in Maritech Cloud, not something tied to one specific product. Today it covers areas including Purchase & Sales, Master Data (customers, items, warehouses, and other reference data), and Transport Management (TMS) resources such as orders and trips — and it continues to grow as more applications are connected. For the complete, current list of available endpoints, see the full API reference.
​

This article covers how to request access, authenticate your requests, and find that full reference.
​

Access to the Public API is controlled with an API key. To get one, contact Maritech support and request API access — let them know which system you're integrating and which environment (test or production) you need access for.

Tip: For integrations, we recommend requesting a dedicated user account for the integration rather than reusing a personal user's credentials. In Maritech Cloud this is called a service user. Using a service user keeps the integration's access independent of any one person's account and makes it easier to manage or revoke later.

Treat your API key like a password — don't share it or commit it to source control.
​

Maritech Cloud has separate environments for testing and production. API keys are issued per environment and won't work in the other one, so make sure you request a key for the right environment.
​

We recommend building and testing your integration against the beta environment first, then switching to production once you're ready to go live, using a separate, production API key.

Send your API key as a request header on every call — not as a URL parameter — using one of the following:

or

Each environment has a built-in Swagger UI where you can browse and try out endpoints directly in your browser. Open it with your API key appended as a query parameter:

Replace {api_key} with your own key. The same pattern works for production by swapping in the production base URL. This is convenient for exploring the API, but for your actual integration, use the header-based authentication described above rather than passing the key in the URL.
​

For the complete, up-to-date list of available endpoints and request/response details, see the full API documentation:

https://apidoc.maritech.cloud/

This is the source of truth for what the API currently supports.
​

If you have questions about access, endpoints, or your integration, reach out to Maritech support.