Overview

This node operation retrieves multiple missions from the Everest Transport Management System (TMS) based on various filtering and sorting options. It is useful for scenarios where users need to fetch a list of missions with specific criteria such as client, agent, service, status, date range, and pagination controls. For example, a logistics manager might use this operation to get all ongoing missions for a particular client within a date range, ordered by start date.

Use Case Examples

1. Fetch up to 50 missions starting from the first record, filtered by a specific client and agent, and ordered by start date descending.
2. Retrieve missions that are currently ongoing by hiding finished missions and filtering by specific statuses like 'delivery-ok' or 'pickup'.
3. Search missions containing a specific term and filter them by service type and date range.

Properties

Output

JSON

• missions - Array of mission objects matching the filter criteria, each containing detailed mission data.

Dependencies

• Requires an API key credential for Everest TMS to authenticate and make requests to the Everest API.

Troubleshooting

• Common issues include invalid or expired API credentials, resulting in authentication errors.
• Incorrect filter values or date formats may cause the API to return errors or empty results.
• Pagination parameters (limit and limit_start) must be within valid ranges to avoid errors.

Links

• Everest TMS API Documentation - Official API documentation for Everest Transport Management System, detailing endpoints and parameters for missions.