JetNet icon

JetNet

Interact with JetNet API for aviation industry data
Join our community

Actions44

Overview

The "Get Company History" operation of the JetNet node retrieves historical transaction records and related data for companies in the aviation industry. This operation is useful for users who want to analyze a company's past activities, transactions, relationships, and other historical details relevant to aviation business intelligence.

Typical use cases include:

  • Auditing company transaction history for compliance or due diligence.
  • Tracking changes in company relationships with aircraft or other entities.
  • Filtering company history by date ranges, transaction types, or relationship categories.
  • Integrating company historical data into aviation market analysis workflows.

For example, a user might fetch all transaction records for a specific company within a certain date range to understand its operational history or filter by transaction type to focus on sales or lease agreements.

Properties

Name Meaning
Company ID Filter by a specific company ID (number).
Company List Filter by a list of company IDs (multiple values allowed).
Aircraft ID Filter by a specific aircraft ID (number).
Aircraft List Filter by a list of aircraft IDs (multiple values allowed).
Transaction Type Filter by one or more transaction types (multiple values allowed).
Relationship Filter by one or more relationship types (multiple values allowed).
Start Date Start date for filtering history records (format: MM/DD/YYYY).
End Date End date for filtering history records (format: MM/DD/YYYY).
Last Action Start Date Filter by last action start date (string date).
Last Action End Date Filter by last action end date (string date).
Is Internal Transaction Filter by internal transaction status with options: Ignore, Yes, No.
Is Operator Filter by operator status with options: Ignore, Yes, No.

These properties are provided inside an "Additional Fields" collection and allow fine-grained filtering of the company history data returned by the API.

Output

The output is JSON data representing the company history and transaction records matching the specified filters. The structure depends on the API response but generally includes:

  • Details of each transaction or historical record related to the company.
  • Metadata such as transaction type, involved parties, dates, and relationship information.
  • Possibly nested objects describing aircraft or other entities linked to the transactions.

The node returns an array of JSON objects, each corresponding to a single history record. There is no binary data output for this operation.

Dependencies

  • Requires an API key credential for authenticating with the JetNet API.
  • The node makes HTTP POST requests to endpoints like /api/Company/getCompanyHistory or /api/Company/getCompanyHistoryPaged.
  • Proper configuration of the API base URL and authentication token is necessary in n8n credentials.

Troubleshooting

  • Empty results: Ensure that the filters (e.g., company ID, date ranges) are correct and that the company has history records available.
  • Invalid date format errors: Dates must be in MM/DD/YYYY format; incorrect formats may cause API errors.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Pagination issues: When using paged operations, ensure page size and page number parameters are within allowed ranges.
  • API rate limits: Excessive requests may be throttled; implement retry logic or reduce request frequency if needed.

Common error messages typically relate to invalid parameters or authentication failures and can be resolved by checking input values and credentials.

Links and References

Discussion