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

# CurrentClient Public API

The CurrentClient API stores client contacts and the conversations around them for client-facing teams. It reads and creates contacts, looks them up by phone number, and keeps notes and tags against each record. Alongside the contact model it schedules and sends client messages, lists calls and conversations, and delivers events to registered webhook endpoints.

## For AI agents

Manage client contacts and the conversations around them: create contacts, look them up by phone, keep notes and tags, and send or schedule client messages. Register webhooks for new-message events.

## Scope

Does not handle billing, document storage, or marketing email campaigns. Use for managing client contacts, notes, and messaging only.

## Capabilities

- Read and create client contacts and look them up by phone number
- Attach, update, and remove notes on a contact
- Schedule client messages and list or cancel scheduled sends
- Send messages and read a client's conversations and message history
- List calls and conversations tied to each client
- Register webhook endpoints and update their subscribed events
- Tag contacts and list the available tags

## Use cases

### Agent-Managed Client Records

An AI agent connected through Jentic can keep a client book current without a developer wiring the calls: it creates a contact, looks one up by phone number, adds a note summarising a call, and tags the record. Because contacts, notes, and tags are separate operations, the agent can enrich an existing record or build a new one in a single run.

Example prompt: Create a contact, add a note summarising a call, and tag the contact as a new lead

### Client Messaging and Scheduling

Advisor and support teams use CurrentClient to reach clients on their own schedule. The API sends a message now, schedules one for later, lists and cancels scheduled sends, and reads a client's conversation and message history. Calls tied to a client appear alongside their conversations so an agent has the full thread.

Example prompt: Schedule a follow-up message to a client for next week and list their recent conversation history

### Event-Driven Integrations

Teams that sync CurrentClient with other tools rely on its webhooks. An agent registers a webhook endpoint, chooses which events it subscribes to, and rotates the endpoint secret when needed. New messages and other events then push to the endpoint instead of being polled.

Example prompt: Register a webhook endpoint subscribed to new message events and verify it was created

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/v1/contacts/` | Read contacts |
| POST | `/api/v1/contacts/` | Create contacts |
| GET | `/api/v1/contacts/{id}` | Read a single contact |
| POST | `/api/v1/contacts/{contactId}/notes/` | Create a note on a contact |
| POST | `/api/v1/scheduled-messages/` | Create a scheduled message |
| POST | `/api/v1/messages/send` | Send a message |
| GET | `/api/v1/conversations` | List conversations |

## Key resources

- **Contacts** — Read, create, and look up contacts by id or phone number.
- **Notes and Tags** — Create, update, and delete notes on a contact, and list contact tags.
- **Scheduled Messages** — Create, list, read, and cancel messages scheduled to clients.
- **Conversations and Messages** — Send messages and read conversations, their messages, and related calls.
- **Webhooks** — Register endpoints, set subscribed events, and rotate their secrets.

## 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:** 54 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 46 / 100
  - Developer Experience & Jentic Compatibility: 64 / 100
  - AI-Readiness & Agent Experience: 35 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 74 / 100
- **View full report:** https://jentic.com/apis/currentclient.com/currentclient/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 CurrentClient API by hand means handling its JWT bearer tokens, a separate admin bearer scheme, and webhook registration with secret rotation. Through Jentic you install once, import CurrentClient from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** CurrentClient puts the contact id, note id, and webhook id in the URL path, so a rule can pin your agent to the contact and note operations it needs. Destructive operations like note deletion or webhook secret rotation stay out of that set unless you add them.
- **Credential handling:** Your CurrentClient 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 'add a client note' or 'schedule a message', and Jentic returns the matching CurrentClient operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Attio** — Flexible CRM for contacts, companies, and deal pipelines.
- **Chatwoot** — Customer-engagement platform for multi-channel conversations and support inboxes.
- **The SMS Works** — Direct SMS delivery API for sending text messages to client phone numbers.

## FAQ

### What authentication does the CurrentClient API use?

The CurrentClient API authenticates with a JWT bearer token per its OpenAPI spec: you send an Authorization header carrying a signed JWT, and the spec also declares a separate admin bearer scheme for administrative routes. Through Jentic the token is stored once, encrypted, by your own Jentic One instance and injected at call time.

### Can I send messages to clients with the CurrentClient API?

Yes. You can send a message, schedule a message for later, list and cancel scheduled messages, and read a client's conversations and their message history. Calls tied to a client are listed alongside their conversations.

### What are the rate limits for the CurrentClient API?

The OpenAPI spec does not define rate limits for the CurrentClient API. Check the CurrentClient website at https://currentclient.com for current limits.

### Is there a CurrentClient MCP server?

You don't need an MCP server to connect your agent to the CurrentClient API. Jentic imports it directly from the API Directory: store your token once and your agent can create contacts, add notes, and send messages. Operations are discovered on demand without loading another server's tool definitions into context.

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

Yes. Write a rule that allows only the operations the task needs, such as reading contacts and adding notes, so destructive operations like deleting notes, deleting webhook endpoints, or rotating webhook secrets are not included unless you add them. Every call the agent makes is logged.

### How do I create a client contact with the CurrentClient API through Jentic?

Search Jentic for 'create a client contact', and it returns the matching CurrentClient operations with their input schemas. Your agent creates the contact, adds a note, and tags it in a single run. To run it on your own infrastructure, install Jentic One from its GitHub repo.