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

# Terros API

Terros API for managing accounts, calendars, contacts, dispositions, evaluations, locations, reports, tasks, teams, users, imports, and exports. The API exposes 15 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get user profile, get accounts. Covers 15 operations with apiKey authentication.

## Scope

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

## Capabilities

- Get user profile
- Create contact
- Integrate Terros API into automated workflows
- Query and filter Terros API records by parameters
- Monitor Terros API operational status and events

## Use cases

### Productivity Operations

Use the Terros API to perform productivity operations programmatically. The API provides 15 endpoints covering core functionality including get user profile, get accounts, get calendars.

Example prompt: Call POST `/user/get` to get user profile

### Automated account Management

Automate account operations by combining multiple Terros API endpoints. Agents can get accounts and then get calendars in a single workflow.

Example prompt: Call GET /account to get accounts, then verify the result

### AI Agent Integration via Jentic

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

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/user/get` | Get user profile |
| GET | `/account` | Get accounts |
| GET | `/calendar` | Get calendars |
| POST | `/contact` | Create contact |
| GET | `/contact` | Get contacts |
| GET | `/disposition` | Get dispositions |
| GET | `/evaluation` | Get evaluations |
| GET | `/location` | Get locations |

## Key resources

- **account** — Operations related to account
- **calendar** — Operations related to calendar
- **contact** — Operations related to contact
- **disposition** — Operations related to disposition
- **evaluation** — Operations related to evaluation

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 60 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 83 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 53 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 34 / 100
- **View full report:** https://jentic.com/apis/terros.com/terros/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Terros API by hand means learning its ApiKey Authorization header auth against the api.terros.com host and coding each account, contact, and calendar call yourself. Through Jentic you install once, import the Terros API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Terros carries its lookup and record details in request bodies and query parameters rather than a resource id in the URL path, so limit the agent to the operations it needs, such as reading a user profile or listing contacts. You choose the operations it may call, so creating a contact is not included unless you add it.
- **Credential handling:** Your Terros API key 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 'get a user profile' or 'list contacts', and Jentic returns the matching Terros API 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 Terros API use?

The Terros API uses an API key passed in the `Authorization` header. 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 get user profile with the Terros API?

Yes. Use the POST `/user/get` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Terros 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 get user profile through Jentic?

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

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

The Terros API exposes 15 endpoints covering account, calendar, contact operations.

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

Yes. Because you self-host Jentic One, your own rules decide which Terros API operations and credentials the agent may use. You can allow only read operations such as getting a user profile with POST `/user/get` or listing contacts with GET /contact, while leaving write operations like creating a contact with POST /contact out of scope unless you add them. Since Terros passes its lookup and record details in request bodies and query parameters rather than a resource ID in the URL path, scoping is done at the operation level you explicitly grant.