Maersk Locations Connector

info@ismena.com

Connector Details

Type

Virtual machines, Single VM , BYOL

Runs on

Google Compute Engine

Last Update

24 October, 2024

Category

Overview

The Maersk Locations Connector facilitates providing organizations with reliable access to up-to-date location and carrier-location data. Acting as a secure and lightweight proxy, the connector simplifies interactions between client applications and the Maersk API by managing headers, query parameters, and response formats on behalf of the user.

It supports essential actions such as service availability, location data retrieval for accessing global Maersk location details, and carrier-location lookups for obtaining carrier-specific location information. By centralizing these capabilities, the Maersk Locations Connector provides a single, standardized interface to integrate location-based data into shipping workflows, planning tools, or analytics platforms.

Integration Overview

This document provides a detailed guide for each integration point, its purpose, configuration, and workflow support using the Maersk Locations Connector.

Supported Integration Action Points:

– get_locations: Retrieves a list of available locations.
– get_carrier_location: Retrieves details for a specific carrier location by ID.

Detailed Integration Documentation

Locations Retrieval

Action	get_locations
Purpose	Retrieves a list of available locations from the Maersk API.
Parameters	No parameters required
Configuration	Ensure the connector is configured with the appropriate environment variables, specifically `CONNECTOR_ENV_LOCATIONS_BASE_URL`.
Output	Successful: Returns a JSON object with a list of locations. Failure: Returns a 502 status code with error details (e.g., {"error": "backend request failed"}).
Workflow Example	Execute the get_locations action. Review the response to obtain the list of locations. 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	carrierGeoID (string, required) – The unique identifier for the carrier location (e.g., "12345").
Configuration	Ensure the connector is configured with the appropriate environment variables, specifically `CONNECTOR_ENV_LOCATIONS_BASE_URL`.
Output	Successful: Returns a JSON object with carrier location details. Failure: Returns a 502 status code with error details (e.g., {"error": "backend request failed"}).
Workflow Example	Execute the get_carrier_location action with carrierGeoID=12345. Process the response to retrieve carrier location details. Use the data for carrier-specific logistics or tracking.

Workflow Creation with the Connector

Example Workflow: Location Data Retrieval

1. Retrieve Locations:	- Execute the get_locations action to fetch all available locations. - Process the list for logistics planning or route optimization.
2. Retrieve Carrier Location:	- Execute the get_carrier_location action with a specific carrierGeoID. - Use the details for carrier-specific operations or tracking.

Pricing

bill-and-calculator-2023-11-27-05-25-06-utc 1

Request a Quote

Support

For Technical support please contact us on

custom-connectors-support@isolutions.sa

A tech solution company dedicated to providing innovation thus empowering businesses to thrive in the digital age.

Register to IBM x iSolution Event