JETNET API Integration: Enhancing CRM Efficiency

Introduction

The JETNET API seamlessly integrates JETNET’s extensive aviation data into your CRM, enhancing workflows and maintaining critical relationships between Aircraft, Companies, and Contacts. This white paper outlines the essential steps, use cases, and features of the JETNET API for efficient CRM integration.

Accessing the JETNET API

Swagger Page

The API’s Swagger documentation is available at: https://customer.jetnetconnect.com/swagger/index.html

Authentication

To use the API, you need valid credentials (email and password) provided by JETNET. Authentication is handled via the APILogin endpoint.

Endpoint: https://customer.jetnetconnect.com/api/Admin/APILogin

Method: POST

Request Body:

{
"emailAddress": "your_email@example.com",
"password": "your_password"
}

Response: Returns a bearerToken and apiToken for subsequent requests.

Key Endpoints and Use Cases

Aircraft Data

Retrieve detailed aircraft information tailored to your needs.

Endpoint: getCondensedOwnerOperatorPaged

Method: POST

Use Case: Filter Gulfstream aircraft currently for sale.

Request Body:

{
"maketype": "BusinessJet",
"make": "Gulfstream",
"forsale": "True"
}

Response: Provides Aircraft IDs and details.

Companies Associated with Aircraft

Identify companies linked to specific aircraft.

Endpoint: getCompanyList

Method: POST

Use Case: Retrieve companies tied to previously fetched Aircraft IDs.

Request Body:

{
"aircraftid": [14538, 14544, 14552],
"relationship": []
}

Response: Returns associated companies.

Contact Information

Fetch contact details linked to these companies.

Endpoint: getContactList

Method: POST

Use Case: Retrieve contact information based on Aircraft or Company IDs.

Request Body:

{
"aircraftid": [14538, 14544, 14552],
  "contactchanges": "false"
}

Response: Includes names, titles, and contact details.

Relationship Mapping

Establish hierarchical links between Aircraft, Companies, and Contacts.

Endpoint: getRelationships

Method: POST

Use Case: Tie together data for CRM hierarchy.

Request Body:

{
"modList": [75, 77, 79],
  "relationshipchanges": "false"
}

Response: Returns relationship mappings.

 

 

 

 

 

Was this article helpful?

/