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

# Tarvent API

Tarvent is a marketing automation platform providing a GraphQL API for managing accounts, campaigns, contacts, journeys, and more. The API exposes 1 endpoints secured with apiKey authentication.

## For AI agents

Programmatically execute graphql query or mutation. Covers 1 operations with apiKey authentication.

## Scope

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

## Capabilities

- Execute GraphQL query or mutation
- Manage marketing data programmatically
- Integrate Tarvent API into automated workflows
- Query and filter Tarvent API records by parameters
- Monitor Tarvent API operational status and events

## Use cases

### Marketing Operations

Use the Tarvent API to perform marketing operations programmatically. The API provides 1 endpoints covering core functionality including execute graphql query or mutation.

Example prompt: Call POST /graphql to execute graphql query or mutation

### Data Retrieval and Monitoring

Query Tarvent 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 Tarvent API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Tarvent 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 'execute graphql query or mutation', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/graphql` | Execute GraphQL query or mutation |

## Key resources

- **GraphQL** — Operations related to GraphQL

## 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:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 87 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/tarvent.com/tarvent/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 Tarvent API by hand means putting your key in the Authorization header, targeting the developer.tarvent.com GraphQL host, and building your own retry handling around its single /graphql endpoint. Through Jentic you install once, import the Tarvent API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Tarvent API exposes a single GraphQL endpoint where the operation travels in the request body, so scope your agent to the operations it needs, such as running a specific query rather than an arbitrary mutation. You choose what it may send, so write operations are not included unless you add them.
- **Credential handling:** Your Tarvent 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 'execute a GraphQL query' or 'run a mutation', and Jentic returns the matching Tarvent API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mailchimp** — Alternative marketing API
- **Hubspot** — Alternative marketing API

## FAQ

### What authentication does the Tarvent API use?

The Tarvent 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 execute graphql query or mutation with the Tarvent API?

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

### What are the rate limits for the Tarvent 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 execute graphql query or mutation through Jentic?

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

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

The Tarvent API exposes 1 endpoints covering graphql operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent can use. The Tarvent API exposes a single POST /graphql endpoint where the operation travels in the request body, so you can scope the agent to the specific queries it needs rather than allowing arbitrary mutations. Write operations are not available to the agent unless you explicitly grant them.
