canonical: https://jentic.com/apis/swaggerhub.airactive/air-active-api

# 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.

## For AI agents

Programmatically apiv1activitiespost, apiv1activitieseditdeletepost. Covers 3 operations.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- ApiV1ActivitiesPost
- ApiV1ActivitiesEditDeletePost
- ApiV1ActivitiesByIdGet
- Query and filter Air Active API records by parameters
- Monitor Air Active API operational status and events

## Use cases

### Identity and Authentication Operations

Use the Air Active API to perform identity auth operations programmatically. The API provides 3 endpoints covering core functionality including apiv1activitiespost, apiv1activitieseditdeletepost, apiv1activitiesbyidget.

Example prompt: Call POST /api/v1/activities to apiv1activitiespost

### Automated Activities Management

Automate activities operations by combining multiple Air Active API endpoints. Agents can apiv1activitieseditdeletepost and then apiv1activitiesbyidget in a single workflow.

Example prompt: Call POST /api/v1/activities/EditDelete to apiv1activitieseditdeletepost, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Air Active API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'apiv1activitiespost', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /api/v1/activities | ApiV1ActivitiesPost |
| POST | /api/v1/activities/EditDelete | ApiV1ActivitiesEditDeletePost |
| GET | /api/v1/activities/activityById/{activity_id} | ApiV1ActivitiesByIdGet |

## Key resources

- **Activities** — Operations for activities

## Why Jentic

- **Setup:** Wiring the Air Active API by hand means building its activity create, edit-delete, and lookup requests and managing the calls yourself. Through Jentic you install once, import the Air Active API from the API Directory, store any required credential once, and your agent calls it.
- **Permission scoping:** The Air Active API takes its write targets in the request body and exposes an activity id in the path only for read-by-id, so scope by operation: limit the agent to the operations it needs, such as looking up an activity by id. Every operation the agent can run is one you have added to its allowed set, so create and edit-delete are included only if you add them.
- **Credential handling:** Any Air Active API credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create an activity' or 'get an activity by id', and Jentic returns the matching Air Active operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Air Active API use?

The Air Active API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I apiv1activitiespost with the Air Active API?

Yes. Use the POST /api/v1/activities endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Air Active API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I apiv1activitiespost through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'apiv1activitiespost'. Jentic returns the matching Air Active API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Air Active API have?

The Air Active API exposes 3 endpoints covering activities operations.

### Can I limit what my agent is allowed to do with the Air Active API?

Yes. Because you run Jentic One yourself, your own rules decide which Air Active API operations and credentials the agent may use. Scope it by operation: for a read-only agent you can allow just the get-activity-by-id lookup (GET /api/v1/activities/activityById/{activity_id}) and leave out the create and edit-delete calls. Every operation the agent can run, including POST /api/v1/activities and the EditDelete endpoint, is one you have explicitly added to its allowed set.