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

# TalkFurther API

TalkFurther API for senior living community lead management. Track conversations, manage leads, and schedule tours. The API exposes 5 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create lead, list leads. Covers 5 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create lead
- List leads
- Get lead
- Schedule tour
- Monitor TalkFurther API operational status and events

## Use cases

### Communications Operations

Use the TalkFurther API to perform communications operations programmatically. The API provides 5 endpoints covering core functionality including create lead, list leads, get lead.

Example prompt: Call POST /leads to create lead

### Automated Leads Management

Automate leads operations by combining multiple TalkFurther API endpoints. Agents can list leads and then get lead in a single workflow.

Example prompt: Call GET /leads to list leads, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call TalkFurther 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 'create lead', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/leads` | Create lead |
| GET | `/leads` | List leads |
| GET | `/leads/{lead_id}` | Get lead |
| GET | `/leads/{lead_id}/conversations` | Get lead conversations |
| POST | `/tours` | Schedule tour |

## Key resources

- **Leads** — Lead management
- **Conversations** — Conversation tracking
- **Tours** — Tour scheduling

## Why Jentic

- **Setup:** Wiring the TalkFurther API by hand means sending its X-API-Key header on every call and threading lead ids through the nested conversation route yourself. Through Jentic you install once, import the TalkFurther API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** TalkFurther puts the lead id in the URL path (`/leads/{lead_id}/...`), so a rule can pin your agent to one lead: it can read that lead and its conversations and nothing else. You choose the operations it may call, so creating leads or tours is not included unless you add it.
- **Credential handling:** Your TalkFurther 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 'create a lead' or 'read a lead's conversations', and Jentic returns the matching TalkFurther operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the TalkFurther API use?

The TalkFurther API uses an API key passed in the `X-API-Key` 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 lead with the TalkFurther API?

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

### What are the rate limits for the TalkFurther 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 lead through Jentic?

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

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

The TalkFurther API exposes 5 endpoints covering leads, conversations, tours operations.

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

Yes. Because you run Jentic One self-hosted, your own rules decide which TalkFurther operations and credentials the agent may use. Since TalkFurther puts the lead id in the URL path (`/leads/{lead_id}/...`), you can pin the agent to a single lead so it only reads that lead and its conversations. You choose the operations it can call, so creating leads with POST /leads or scheduling tours with POST /tours stays off unless you explicitly grant it.