canonical: https://jentic.com/apis/targa.ai/targa

# Targa API

Targa AI project management API for creating, managing, and tracking elements including groups, goals, strategies, initiatives, and action items. The API exposes 7 endpoints secured with bearer authentication.

## For AI agents

Programmatically create an element, get element by id. Covers 7 operations with bearer authentication.

## Scope

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

## Capabilities

- Create an element
- Get element by ID
- Update an element
- Delete an element
- Monitor Targa API operational status and events

## Use cases

### Analytics Operations

Use the Targa API to perform analytics operations programmatically. The API provides 7 endpoints covering core functionality including create an element, get element by id, update an element.

Example prompt: Call POST /elements to create an element

### Automated Elements Management

Automate elements operations by combining multiple Targa API endpoints. Agents can get element by id and then update an element in a single workflow.

Example prompt: Call GET `/elements/{element_id}` to get element by id, then verify the result

### AI Agent Integration via Jentic

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

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/elements` | Create an element |
| GET | `/elements/{element_id}` | Get element by ID |
| PATCH | `/elements/{element_id}` | Update an element |
| DELETE | `/elements/{element_id}` | Delete an element |
| GET | `/elements/root/{root_id}` | Get element by root ID |
| GET | `/elements/history` | Get element history |
| GET | `/elements/notification/recievers/{element_id}` | Get element notification receivers |

## Key resources

- **Elements** — Element CRUD operations
- **History** — Element history tracking
- **Notifications** — Notification receiver management

## 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:** 74 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 58 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/targa.ai/targa/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 Targa API by hand means managing its JWT bearer auth, targeting the production.api.targa.ai host, and handling retries on element calls yourself. Through Jentic you install once, import the Targa API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Targa API puts the element id in the URL path (`/elements/{element_id}`), so a rule can pin your agent to one element: it can read that element and its history. You choose the operations it may call, so destructive ones like deleting an element or patching it are not included unless you add them.
- **Credential handling:** Your Targa API 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 element' or 'get element history', and Jentic returns the matching Targa API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the Targa API use?

The Targa API uses a Bearer token 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 create an element with the Targa API?

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

### What are the rate limits for the Targa 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 create an element through Jentic?

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

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

The Targa API exposes 7 endpoints covering elements, history, notifications operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Targa API operations and credentials your agent may use. Since the Targa API carries the element id in the URL path, such as `/elements/{element_id}`, you can pin the agent to a single element and let it only read that element and its history through GET `/elements/{element_id}` and GET `/elements/history.` You pick the operations it may call, so destructive ones like DELETE `/elements/{element_id}` or PATCH `/elements/{element_id}` stay out of reach unless you grant them.