JetNet icon

JetNet

Interact with JetNet API for aviation industry data

Overview

This node integrates with the JetNet API to retrieve detailed aviation industry data. Specifically, the "Get Airframe" operation under the "Aircraft" resource fetches comprehensive airframe information for a specified aircraft by its unique ID. This is useful for aviation professionals, maintenance teams, and fleet managers who need up-to-date structural details about an aircraft's frame.

Practical examples include:

  • Retrieving airframe specifications before maintenance or inspection.
  • Verifying airframe details during aircraft acquisition or leasing processes.
  • Integrating airframe data into aviation management systems for reporting or analytics.

Properties

Name Meaning
Aircraft ID The unique identifier of the aircraft for which the airframe information is requested.

Output

The output contains a JSON object representing the airframe information of the specified aircraft. The structure corresponds directly to the data returned by the JetNet API endpoint for airframe details. It typically includes fields such as airframe type, dimensions, serial numbers, manufacturing details, and other relevant structural attributes.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the JetNet API service.
  • Requires an API authentication token credential configured in n8n to authorize requests.
  • The base URL for API requests is https://customer.jetnetconnect.com.
  • The node uses HTTP GET method to fetch airframe data from the endpoint /api/Aircraft/getAirframe/{aircraftId}/{apiToken}.

Troubleshooting

  • Common issues:

    • Invalid or missing Aircraft ID will result in errors or empty responses.
    • Expired or incorrect API authentication token may cause authorization failures.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:

    • Authorization errors typically indicate issues with the API token; verify and update credentials.
    • "Not Found" errors suggest the provided Aircraft ID does not exist or is incorrect.
    • Timeout or network errors require checking internet connectivity and JetNet service status.
  • Resolution tips:

    • Ensure the Aircraft ID is correct and exists in the JetNet database.
    • Confirm that the API key credential is valid and has necessary permissions.
    • Use the node’s "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

Discussion