canonical: https://jentic.com/apis/aire.link/aire-link

# AIRe Link API

Jentic publishes the only available OpenAPI specification for AIRe Link API, keeping it validated and agent-ready. AIRe Link is a remote assistance platform that connects field workers with experts via video calls and AR-style guidance, generally launched by sending a one-time link or QR code to the user. The API exposes 24 endpoints covering accounts, calls, contacts, devices, messages, QR codes, exports, webhooks, and team and worker management. Authentication is via bearer token.

## For AI agents

Initiate remote assistance video calls, generate QR-coded session links, and manage workers, devices, and webhooks for AIRe Link.

## Scope

Does not handle outbound voice calls, SMS, or general team chat - use for QR-launched remote assistance video sessions and related worker management only.

## Capabilities

- Initiate remote assistance calls and list active or historical sessions via /calls
- Generate and manage QR codes that launch a session when scanned by a user
- Manage workers, teams, and contacts who can be invited into a call
- Maintain a registry of connected devices for fleet-style remote support
- Create and read messages tied to a remote assistance session
- Register webhooks for call, message, and worker lifecycle events
- Export session data for compliance and reporting

## Use cases

### Field Worker Remote Assistance

Connect a remote expert to a field worker by sending a one-time link via SMS, email, or QR code. POST /calls creates a call session, POST /qr-codes generates a launch QR for printed materials or stickers on equipment, and POST /messages records guidance text exchanged during the session.

Example prompt: Create a call inviting contact c_99 with subject 'pump line 4 repair', generate a QR code linking to that call, and send the QR url to the worker's email

### QR-Launched Equipment Support

Place QR codes on physical equipment so anyone can launch a support call by scanning. POST /qr-codes creates a code tied to an account and asset reference, GET /qr-codes lists active codes for a fleet, and the call generated from a scan appears in /calls with the originating QR code captured.

Example prompt: Generate a QR code for asset_serial=SN-7842 with a default subject of 'Generator service request', then list all calls launched from that QR in the last 30 days

### Compliance Export and Webhook Audit

Subscribe to webhook events for every call and message, then run scheduled exports for retention. POST /webhooks registers an endpoint to receive call.started, call.ended, and message.created events, and POST /exports queues an export of call data over a date range for compliance archival.

Example prompt: Register a webhook at https://hooks.example.com/aire for call.ended events, then create an export of all calls between 2026-05-01 and 2026-05-31

### AI Agent Remote Support Coordinator

An agent triaging an inbound issue can spin up an AIRe Link call, attach the right contact, and dispatch a QR code automatically - through Jentic the bearer token stays in the vault and the agent only handles scoped operations.

Example prompt: Search Jentic for 'create an aire link call', load the POST /calls schema, create a call with contact c_99 and subject 'urgent line stoppage', and return the join URL

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /calls | Create a remote assistance call |
| GET | /calls | List calls |
| POST | /qr-codes | Create a QR code that launches a session |
| GET | /qr-codes | List QR codes |
| POST | /contacts | Create a contact |
| POST | /webhooks | Register a webhook subscription |
| POST | /exports | Create an export of call or message data |

## Key resources

- **Calls** — Remote assistance video sessions and their participants
- **QR Codes** — Codes that launch a call when scanned, often tied to an asset or contact
- **Contacts** — Customer or end-user contacts invited into calls
- **Workers** — Internal experts who can join sessions and be assigned to teams
- **Teams** — Worker groupings used for routing and reporting
- **Devices** — Connected hardware registered to workers
- **Messages** — Messages exchanged inside a remote assistance session
- **Webhooks** — Subscriptions for call, message, and worker lifecycle events
- **Exports** — Bulk exports of call data for compliance and reporting

## Why Jentic

- **Setup:** Wiring AIRe Link by hand means handling its bearer token, building call and QR-code payloads, and writing your own retry logic. Through Jentic you install once, import AIRe Link from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** AIRe Link carries its call, QR-code, and contact details in the request body, so scope your agent by operation: limit it to the operations it needs, such as creating a call, and leave out webhook or export endpoints it does not use.
- **Credential handling:** Your AIRe Link bearer token 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 aire link call', and Jentic returns the matching operation with its schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio Video API** — Programmable video rooms suitable for custom remote assistance workflows
- **Aircall Public API** — Pair AIRe Link video sessions with Aircall voice telephony for full omnichannel support
- **Zendesk API** — Log AIRe Link sessions back to support tickets in Zendesk

## FAQ

### Why is there no official OpenAPI spec for AIRe Link API?

AIRe Link does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AIRe Link API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the AIRe Link API use?

AIRe Link uses HTTP bearer token authentication. Jentic stores the bearer token encrypted in the vault and adds the Authorization header on each call, so the agent never handles the raw token.

### Can I create a QR code that launches a call with the AIRe Link API?

Yes. POST /qr-codes creates a code that, when scanned, opens an AIRe Link session. The code can carry a default subject and contact, making it suitable for printing onto equipment or service kits.

### What are the rate limits for the AIRe Link API?

The spec does not declare formal rate limits. Treat /calls and /qr-codes as user-driven endpoints used at human pace; for bulk operations, prefer /exports rather than looping list calls.

### How do I start a remote assistance call with the AIRe Link API through Jentic?

Run pip install jentic, search Jentic for 'create aire link call', load the schema for POST /calls, then execute with the contact ID and subject. Jentic applies the bearer Authorization header automatically.

### Can I export call history for compliance with the AIRe Link API?

Yes. POST /exports queues an export for a date range and resource type, and GET /exports lists previously generated exports so they can be downloaded for retention archives.

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

Yes. Jentic One runs self-hosted, so your own rules decide which AIRe Link operations and credentials the agent may use. Because AIRe Link scopes access by operation rather than by token, you can grant only the endpoints a task needs, such as POST /calls to start a session and POST /qr-codes to launch one, while leaving out POST /webhooks and POST /exports. The agent can then create calls and QR codes without ever being able to register webhooks or run compliance exports.