canonical: https://jentic.com/apis/thirdlane.com/thirdlane

# Thirdlane API

Thirdlane communications platform REST API for managing admins, agents, IVR, queues, tenants, extensions, schedules, inbound routes, and DIDs. The API exposes 2 endpoints secured with basic authentication.

## For AI agents

Programmatically add admin, delete admin. Covers 2 operations with basic authentication.

## Scope

Does not handle payments, communications, or crm - use for productivity only.

## Capabilities

- Add admin
- Delete admin
- Integrate Thirdlane API into automated workflows
- Query and filter Thirdlane API records by parameters
- Monitor Thirdlane API operational status and events

## Use cases

### Productivity Operations

Use the Thirdlane API to perform productivity operations programmatically. The API provides 2 endpoints covering core functionality including add admin, delete admin.

Example prompt: Call POST `/api/admin/{tenant}` to add admin

### Data Retrieval and Monitoring

Query Thirdlane API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Thirdlane API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Thirdlane 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 basic tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/admin/{tenant}` | Add admin |
| DELETE | `/api/admin/{tenant}/{name}` | Delete admin |

## Key resources

- **Admin** — Operations related to Admin

## Why Jentic

- **Setup:** Wiring the Thirdlane API by hand means encoding your username and password for basic auth, sending that header on each call, and handling your own retries. Through Jentic you install once, import the Thirdlane API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** The Thirdlane API puts the tenant in the URL path (`/api/admin/{tenant}`), so a rule can pin your agent to one tenant: it acts only within that tenant. You choose the operations it may call, so destructive actions like deleting an admin are not included unless you add them.
- **Credential handling:** Your Thirdlane credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'add an admin to a tenant', and Jentic returns the matching Thirdlane operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana** — Alternative productivity API
- **Monday** — Alternative productivity API
- **Clickup** — Complementary productivity API

## FAQ

### What authentication does the Thirdlane API use?

The Thirdlane API uses HTTP Basic authentication with username and password. 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 add admin with the Thirdlane API?

Yes. Use the POST `/api/admin/{tenant}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Thirdlane 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 add admin through Jentic?

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

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

The Thirdlane API exposes 2 endpoints covering admin operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Thirdlane operations and credentials the agent may use. Since the tenant sits in the URL path (`/api/admin/{tenant}`), a rule can pin the agent to a single tenant so it acts only within that tenant. You also choose which operations it may call, so you can grant POST `/api/admin/{tenant}` to add an admin while withholding DELETE `/api/admin/{tenant}/{name}` unless you explicitly add it.