Swaggerhub Airactive APIs
2 APIs14 Endpoints1 Category
Categories
API Catalog
Air Active API
This document aims at providing a complete and exhaustive description of AirActive API. Clients connecting to Air Active service needs to fetch a valid token to initiate the communication. The token will be used and injected in all the query as an Authorization header field. If the client fails to login then a 401 error code is sent as a response (Unauthorized). The API exposes 3 endpoints.
3 endpointsAirActivePro API
This document aims at providing a complete and exhaustive description of AirActive API. Clients connecting to Air Active service needs to fetch a valid token to initiate the communication. The token will be used and injected in all the query as an Authorization header field. If the client fails to login then a 401 error code is sent as a response (Unauthorized). The API exposes 11 endpoints.
11 endpointsConnect Your Agent
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.