Custom Connector
Maersk Locations Connector
Global
The Maersk Locations Connector provides organizations with reliable access to up-to-date location and carrier-location data. Acting as a secure, lightweight proxy, it manages headers, query parameters, and response formats on behalf of the user, offering a single standardized interface to integrate location-based data into shipping workflows, planning tools, or analytics platforms.
Overview
Integration Overview
This document provides a detailed guide for each integration point, its purpose, configuration, and workflow support using the Maersk Locations Connector.
- get_locations. Retrieves a list of available locations.
- get_carrier_location. Retrieves details for a specific carrier location by ID.
Documentation
Detailed Integration Documentation
Locations Retrieval
| Action | get_locations |
|---|---|
| Purpose | Retrieves a list of available locations from the Maersk API. |
| Parameters | No parameters required. |
| Configuration | Configure the connector with the appropriate environment variables, specifically CONNECTOR_ENV_LOCATIONS_BASE_URL. |
| Output | Successful: JSON object with a list of locations. Failure: 502 status code with error details (e.g. {“error”: “backend request failed”}). |
| Workflow example | Execute get_locations, review the response to obtain the list of locations, and use the data for location-based applications or logistics planning. |
Carrier Location Retrieval
| Action | get_carrier_location |
|---|---|
| Purpose | Retrieves detailed information for a specific carrier location based on the carrier Geo ID. |
| Parameters | Required: carrierGeoID (string) – the unique identifier for the carrier location (e.g. “12345”). |
| Configuration | Configure the connector with the appropriate environment variables, specifically CONNECTOR_ENV_LOCATIONS_BASE_URL. |
| Output | Successful: JSON object with carrier location details. Failure: 502 status code with error details. |
| Workflow example | Execute get_carrier_location with carrierGeoID=12345, process the response to retrieve carrier location details, and use the data for carrier-specific logistics or tracking. |
Example Workflow: Location Data Retrieval
| Retrieve locations | Execute get_locations to fetch all available locations, then process the list for logistics planning or route optimization. |
|---|---|
| Retrieve carrier location | Execute get_carrier_location with a specific carrierGeoID and use the details for carrier-specific operations or tracking. |
Support
For technical support, contact custom-connectors-support@isolutions.sa.