canonical: https://jentic.com/apis/ctt.pt/ctt

# Ctt Pt CRM Accounts API

The CTT CRM Accounts API views, creates, and updates account records in the CTT CRM, with each account identified by its party number. It lists all accounts, reads a single account, creates a new one, and applies partial updates. Each account can also carry attachments: an agent can list, upload, read, and remove documents tied to an account. The API is served from the CTT CRM REST host and secured with client credentials.

## For AI agents

View, create, and update CRM account records in the CTT CRM by party number, and list, upload, read, and remove attachments on an account.

## Scope

Does not handle deals, pipelines, or email campaigns. Use for managing CTT CRM account records and their attachments only.

## Capabilities

- List all accounts in the CTT CRM
- Read a single account by its party number
- Create a new account record
- Apply a partial update to an account
- List and upload attachments on an account
- Read or remove a specific attachment on an account

## Use cases

### Agent account maintenance

An AI agent connected through Jentic reads an account by its party number, applies a partial update such as a changed contact detail, and confirms the change, without a human opening the CRM. It can also create a new account record when one does not yet exist.

Example prompt: Read an account by its party number, apply a partial update to a contact field, and read it back to confirm

### Document attachment management

A back-office workflow attaches supporting documents to an account, lists the existing attachments, and removes an outdated one. The CRM Accounts API exposes attachment operations under each account so an agent can keep an account's documents current.

Example prompt: Upload a document attachment to an account and then list its attachments to confirm it was stored

### Account directory sync

A sync job lists all accounts to mirror the CRM directory into another system, then creates missing accounts as they appear. Listing accounts and creating new ones from the same API keeps the external copy aligned with the CTT CRM.

Example prompt: List all accounts and create any that are missing in the downstream system

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/accounts` | List all accounts |
| POST | `/accounts` | Create an account |
| GET | `/accounts/{PartyNumber}` | Get an account by party number |
| PATCH | `/accounts/{PartyNumber}` | Apply a partial update to an account |
| GET | `/accounts/{PartyNumber}/child/Attachment` | List attachments on an account |
| POST | `/accounts/{PartyNumber}/child/Attachment` | Upload an attachment to an account |

## Key resources

- **Accounts** — List, read, create, and update account records by party number
- **Attachments** — List, upload, read, and remove documents tied to an account

## 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:** 53 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 72 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 36 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 44 / 100
- **View full report:** https://jentic.com/apis/ctt.pt/ctt/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 CTT CRM Accounts API by hand means configuring client-id and client-secret credentials against the CRM REST host and learning the party-number account model with its attachment child resource. Through Jentic you install once, import the CTT CRM Accounts API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** The CTT CRM Accounts API carries the party number in the URL path for single-account operations, and rules bound which operations your agent may call. You choose the operations it may call, so it can read and list accounts without being able to create accounts or remove attachments unless you add those.
- **Credential handling:** Your CTT CRM client 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 'update a CRM account' or 'upload an attachment', and Jentic returns the matching CTT CRM operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **HubSpot CRM Companies** — HubSpot's Companies API manages company account records in the HubSpot CRM.
- **Close** — Close is a sales CRM with leads, contacts, and account records.
- **Copper** — Copper manages CRM contacts and pipelines that can sit alongside CTT account records.

## FAQ

### What authentication does the CTT CRM Accounts API use?

The CTT CRM Accounts API is secured with client credentials, a client-id and client-secret pair sent with each request, per its OpenAPI spec. Through Jentic those credentials are stored once by your own self-hosted instance and injected when a call runs, so they never appear in the agent's prompt or logs.

### Can I update an account with the CTT CRM Accounts API?

Yes. Read an account by its party number, then apply a partial update with the PATCH operation to change the fields you need. You can also create a new account or list all accounts from the same API.

### Can I limit what my agent is allowed to do with the CTT CRM Accounts API?

Yes. Write a rule that allows only the operations the agent needs, for example reading and listing accounts, so it cannot create accounts or remove attachments, and every call it makes is logged. Add write operations only when the task requires them.

### What are the rate limits for the CTT CRM Accounts API?

The OpenAPI spec does not specify rate limits. Check the CTT CRM integration documentation for current limits before running bulk account listing or sync jobs.

### Is there a CTT CRM Accounts MCP server?

You don't need an MCP server to give your agent the CTT CRM Accounts API. Jentic connects it directly from the API Directory: import it, store the credentials once, and your agent calls the account and attachment operations on demand without loading another server's tool definitions into its context.

### How do I update an account with the CTT CRM Accounts API through Jentic?

Search Jentic by intent such as 'update a CRM account', and Jentic returns the account update operation with its input schema so your agent passes the party number and changed fields. To run it on your own infrastructure, install Jentic One from its GitHub repo.