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

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

## For AI agents

Programmatically apiv1authforgotpasswordpost, apiv1authloginpost. Covers 11 operations.

## Scope

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

## Capabilities

- ApiV1AuthForgotPasswordPost
- ApiV1AuthLoginPost
- ApiV1AuthRefreshTokenPost
- ApiV1AuthCoachPost
- ApiV1AuthResendCodePost
- ApiV1AuthResetPasswordPost
- ApiV1AuthVerificationCodePost

## Use cases

### Identity and Authentication Operations

Use the AirActivePro API to perform identity auth operations programmatically. The API provides 11 endpoints covering core functionality including apiv1authforgotpasswordpost, apiv1authloginpost, apiv1authrefreshtokenpost.

Example prompt: Call POST /api/v1/auth/forgot_password to apiv1authforgotpasswordpost

### Automated Auth Management

Automate auth operations by combining multiple AirActivePro API endpoints. Agents can apiv1authloginpost and then apiv1authrefreshtokenpost in a single workflow.

Example prompt: Call POST /api/v1/auth/login to apiv1authloginpost, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call AirActivePro 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 'apiv1authforgotpasswordpost', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /api/v1/auth/forgot_password | ApiV1AuthForgotPasswordPost |
| POST | /api/v1/auth/login | ApiV1AuthLoginPost |
| POST | /api/v1/auth/refresh_token | ApiV1AuthRefreshTokenPost |
| POST | /api/v1/auth/register_coach | ApiV1AuthCoachPost |
| POST | /api/v1/auth/resend_code | ApiV1AuthResendCodePost |
| POST | /api/v1/auth/reset_password | ApiV1AuthResetPasswordPost |
| POST | /api/v1/auth/verification_code | ApiV1AuthVerificationCodePost |
| GET | /api/v1/coaches | ApiV1CoachesGet |

## Key resources

- **Auth** — Operations related to Auth
- **Coaches** — Operations related to Coaches
- **Providers** — Operations related to Providers
- **Users** — Operations related to Users

## Why Jentic

- **Setup:** Wiring AirActivePro by hand means standing up its account flows yourself: registering coaches, exchanging login and refresh tokens against the hosted host, and resending verification codes on your own. Through Jentic you install once, import AirActivePro from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** AirActivePro's auth operations carry their target in the request body rather than the URL path, so limit the agent to the operations it needs, such as login and refresh token. You choose the operations it may call, so account-changing ones like reset password or register coach are not included unless you add them.
- **Credential handling:** Your AirActivePro 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 'log a coach in' or 'refresh an access token', and Jentic returns the matching AirActivePro 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 AirActivePro API use?

The AirActivePro 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 apiv1authforgotpasswordpost with the AirActivePro API?

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

### What are the rate limits for the AirActivePro 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 apiv1authforgotpasswordpost through Jentic?

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

### How many endpoints does the AirActivePro API have?

The AirActivePro API exposes 11 endpoints covering auth, coaches, providers operations.

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

Yes. Because you run Jentic One self-hosted, your own rules decide which AirActivePro operations and credentials the agent may use. You can allow only the operations it needs, such as login and refresh token, and leave account-changing calls like reset password or register coach out unless you add them. Since these operations carry their target in the request body rather than the URL path, scoping happens at the operation level, so the agent can call only what you have permitted.