canonical: https://jentic.com/apis/swaggerhub.trin/account-api

# Trin Account API

Account API is to update account information. The API exposes 1 endpoints.

## For AI agents

Programmatically update sales contact and customer service contact details. Covers 1 operations.

## Scope

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

## Capabilities

- Update Sales Contact and Customer Service Contact details
- Manage developer tools data programmatically
- Integrate Account API into automated workflows
- Query and filter Account API records by parameters
- Monitor Account API operational status and events

## Use cases

### Developer Tools Operations

Use the Account API to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including update sales contact and customer service contact details.

Example prompt: Call PATCH /account to update sales contact and customer service contact details

### Data Retrieval and Monitoring

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

### AI Agent Integration via Jentic

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

Example prompt: Search Jentic for 'update sales contact and customer service contact details', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| PATCH | /account | Update Sales Contact and Customer Service Contact details |

## Key resources

- **account** — Operations related to account

## Why Jentic

- **Setup:** Wiring the Account API by hand means pointing at its SwaggerHub host and handling its single account patch with your own retries, even though it exposes no auth scheme. Through Jentic you install once, import Account from the API Directory, store the connection details once, and your agent calls it.
- **Permission scoping:** Limit the agent to the operations it needs, such as updating account contact details, rather than the whole surface. Because you pick the allowed operations, the agent only ever runs the calls you authorize.
- **Credential handling:** Any connection details for Account 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 'update sales and customer service contact details', and Jentic returns the matching Account operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Account API use?

The Account API uses no authentication. 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 update sales contact and customer service contact details with the Account API?

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

### What are the rate limits for the Account 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 update sales contact and customer service contact details through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'update sales contact and customer service contact details'. Jentic returns the matching Account API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

The Account API exposes 1 endpoints covering account operations.

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

Yes. Because Jentic One is self-hosted, you run it under your own rules, and you decide which Account API operations and credentials the agent may use. The Account API exposes a single operation, PATCH /account to update sales contact and customer service contact details, so you can authorize just that call and withhold everything else. The agent can only run the operations you have allowed, and any connection details are injected at execution time rather than exposed to the agent.