API Access & Credentials
All customers using JETNET API must access it with valid credentials (username and password), obtained via a JETNET API subscription. For subscription inquiries, please contact sales.
API Design
JETNET API returns results in JSON (JavaScript Object Notation) format. JSON is a human-readable, open-standard format ideal for transmitting data objects via key/value pairs and arrays.
Connection & Testing
Before production use, we recommend testing API calls via our Swagger interface: Swagger UI. It provides request samples, live testing, and field details.
Accessing JETNET API
The API base URL is: https://customer.jetnetconnect.com/api/
Helpful Links
Using Swagger to Explore the API
💡 Try the API in your browser using Swagger UI
You can explore and test live API endpoints via the JETNET Swagger UI.
- Scroll to
/Utility/APILoginand click “Try it out”. -
Enter your API login credentials:
{ "emailaddress": "you@example.com", "password": "your_password" } - Click Execute and copy the returned bearer token.
- Click the Authorize button at the top of the page.
- Paste your token in the following format:
Bearer your_token_here - Click Authorize again, then close the window.
- You can now use any endpoint by entering your securityToken as needed.
Note: Tokens expire after 60 minutes of inactivity. Re-authenticate with /APILogin if needed.
Standard API Endpoints/Requests
Login/Connection to the Customer API
Refer to the swagger open API page for examples using the link below. https://customer.jetnetconnect.com/swagger/index.html
Sample programs/code are available from the following Github link. https://github.com/jetnet-llc/jtcTestClient
Understanding API Responses
Every API response from JETNET includes two standard fields that provide metadata about the result:
- responseid – A unique identifier assigned to every response. This ID is useful for tracing and logging individual API calls.
-
responsestatus – Indicates whether the request succeeded or failed. This field typically starts with:
-
Success:– The request was processed successfully -
ERROR:– An error occurred, followed by a message providing more detail
-
If the securityToken has expired, for example, the API will return:
ERROR: INVALID SECURITY TOKENIn that case, your application should call /Utility/APILogin again to obtain a new token before retrying the request.