JetNet icon

JetNet

Interact with JetNet API for aviation industry data
Join our community

Actions44

Overview

The "Get Company History Paged" operation of the JetNet node retrieves paginated historical transaction and event records related to companies in the aviation industry. This operation is useful for users who want to analyze or audit company activities over time, such as ownership changes, certifications, relationships, or other transactional history.

Typical use cases include:

  • Fetching a manageable subset of company history data page-by-page to avoid overwhelming API responses.
  • Filtering company history by specific criteria like company IDs, aircraft involved, transaction types, date ranges, and relationship types.
  • Integrating company historical data into aviation market analysis, compliance checks, or CRM systems.

For example, a user might retrieve the second page of 100 company history records filtered to only show transactions involving certain aircraft or within a specific date range.

Properties

Name Meaning
Page Size Number of results per page (minimum 1, maximum 1000). Controls how many history records are returned in one API call.
Page Page number to retrieve (minimum 1). Specifies which page of results to fetch.
Additional Fields Collection of optional filters to refine the company history query:
- Company ID Filter by a specific company ID (number).
- Company List Filter by multiple company IDs (array of strings).
- Aircraft ID Filter by a specific aircraft ID (number).
- Aircraft List Filter by multiple aircraft IDs (array of strings).
- Transaction Type Filter by one or more transaction types (array of strings).
- Relationship Filter by one or more relationship types (array of strings).
- Start Date Start date for filtering history records (string in MM/DD/YYYY format).
- End Date End date for filtering history records (string in MM/DD/YYYY format).
- Last Action Start Date Filter by last action start date (string).
- Last Action End Date Filter by last action end date (string).
- Is Internal Transaction Filter by internal transaction status with options: Ignore, Yes, No.
- Is Operator Filter by operator status with options: Ignore, Yes, No.

Output

The output is an array of JSON objects representing individual company history records matching the specified filters and pagination parameters. Each item contains detailed information about a single historical transaction or event related to a company.

The exact structure of each record depends on the API response but typically includes fields such as transaction type, involved companies and aircraft, dates, relationships, and other metadata relevant to the company's history.

No binary data output is produced by this operation.

Dependencies

  • Requires an active API key credential for authenticating requests to the JetNet API.
  • The node must be configured with the base URL https://customer.jetnetconnect.com and appropriate headers for JSON content.
  • Pagination parameters (pageSize and page) must be provided to control the size and offset of the result set.

Troubleshooting

  • Common issues:

    • Providing invalid or missing API credentials will cause authentication failures.
    • Requesting a page number beyond the available pages may return empty results.
    • Incorrect date formats in filters can lead to API errors or no results.
    • Using incompatible filter combinations might yield no data.

  • Error messages:

    • Authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
    • Validation errors: Check that numeric fields like pageSize, page, and IDs are within allowed ranges.
    • Network or timeout errors: Ensure stable internet connection and that the JetNet API endpoint is reachable.

  • To resolve errors, confirm all required parameters are correctly set, especially pagination and filter fields, and retry the request.

Links and References

Discussion