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

# Cincpro CINC Open API

Jentic publishes the only available OpenAPI specification for CINC Open API, keeping it validated and agent-ready. The CINC Open API exposes the lead, contact, and activity records held inside the CINC (Commissions Inc) real estate CRM so external tools and AI agents can read and update pipeline data. It covers listing and creating leads, retrieving and updating individual lead records, and reading contact and activity history through a small set of REST endpoints under api.cincpro.com. Authentication is by an X-API-Key header issued from a CINC account, making it suitable for back-office automations, lead routing, and reporting integrations.

## For AI agents

Read and write real estate leads, contacts, and activities in the CINC CRM so an agent can route new prospects, sync follow-ups, and pull pipeline reports.

## Scope

Does not handle MLS listing data, transaction management, or commission disbursement - use for CINC CRM lead, contact, and activity records only.

## Capabilities

- List leads from the CINC CRM with pagination and filter parameters
- Create a new lead record via POST /leads when a prospect arrives from a website or campaign
- Retrieve a single lead by leadId for enrichment or qualification checks
- Update an existing lead record (status, notes, assigned agent) through PUT `/leads/{leadId}`
- Pull contact records from /contacts to sync the CINC database with external systems
- Read activity history through /activities to build follow-up reports and timelines

## Use cases

### Website lead capture into CINC

When a visitor submits a property enquiry form, the new lead is posted directly into the CINC CRM via POST /leads with name, email, phone, and source fields. The lead is assigned to the right agent and appears in the CINC pipeline within seconds, removing the manual copy step between the website and the CRM. A lightweight integration can be live in a single afternoon.

Example prompt: Call POST /leads with a JSON body containing name, email, phone, and source 'website-form' and confirm the returned leadId.

### Pipeline reporting and lead enrichment

Listing leads via GET /leads and pulling individual records by leadId lets an analyst or agent build daily pipeline reports without exporting CSVs from the CINC UI. Activities pulled from /activities provide the timeline needed to flag stale leads or measure follow-up speed.

Example prompt: List the most recent 50 leads from GET /leads, fetch /activities for each leadId, and flag any lead with no activity in the past 7 days.

### Lead status sync with phone and SMS tools

When an agent finishes a call with a prospect, the call disposition is written back to CINC by calling PUT `/leads/{leadId}` with the new status and notes. This keeps the CRM aligned with the dialer or messaging tool so no manual update is required between systems.

Example prompt: Update lead 12345 in CINC by calling PUT `/leads/12345` with status 'contacted' and a note summarising the call outcome.

### AI agent triage of inbound leads via Jentic

An AI agent loaded with the CINC tool through Jentic searches by intent ('create a real estate lead'), receives the POST /leads schema, and pushes qualified prospects into CINC while logging an activity entry. The agent never sees the raw API key - Jentic resolves credentials at execution time.

Example prompt: Use the Jentic search 'create a real estate lead in CINC', load the schema for POST /leads, and execute the call with the qualified prospect's contact details.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/leads` | List leads |
| POST | `/leads` | Create a new lead |
| GET | `/leads/{leadId}` | Get a single lead |
| PUT | `/leads/{leadId}` | Update a lead |
| GET | `/contacts` | List contacts |
| GET | `/contacts/{contactId}` | Get a single contact |
| GET | `/activities` | List activities |

## Key resources

- **Leads** — List, create, retrieve, and update lead records in the CINC sales pipeline
- **Contacts** — List and retrieve contact records, the longer-term identity of a person in CINC
- **Activities** — List activity history (calls, emails, status changes) logged against leads and contacts

## Why Jentic

- **Setup:** Wiring the CINC Open API by hand means managing its API key and threading lead, contact, and activity records through the right CRM endpoints yourself. Through Jentic you install once, import the CINC Open API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** CINC puts the lead and contact id in the URL path (`/leads/{leadId}`, `/contacts/{contactId}`), so a rule can pin your agent to reading and updating specific records. You choose the operations it may call, so creating new leads or writing contacts is not included unless you add it.
- **Credential handling:** Your CINC 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 'look up a CRM lead' or 'log an activity on a contact', and Jentic returns the matching CINC operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **HubSpot CRM Objects** — General-purpose CRM object API used by many real estate teams as a CINC replacement
- **Clarkup API** — Lightweight lead-creation API that can feed prospects into CINC alongside Clarkup's own pipeline
- **Mailchimp Marketing API** — Email marketing platform used to nurture CINC leads after capture

## FAQ

### Why is there no official OpenAPI spec for CINC Open API?

CINC (Commissions Inc) does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CINC Open API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the CINC Open API use?

The CINC Open API uses an API key sent in the X-API-Key request header. Through Jentic, the key is held in your encrypted Jentic One instance and is never exposed to the agent's context - Jentic injects the header at execution time.

### Can I create new leads in CINC through the API?

Yes. POST /leads accepts the lead's name, email, phone, source, and other CRM fields and returns the new leadId. This is the primary way to push website forms, marketing campaigns, or third-party prospects into the CINC pipeline.

### Can I read activities or call history for a CINC lead?

Yes. GET /activities returns the activity log entries (calls, emails, status changes) recorded against leads and contacts in CINC, which lets you build follow-up timelines or pipeline-velocity reports.

### What are the rate limits for the CINC Open API?

The published OpenAPI specification does not declare explicit rate limits. CINC enforces account-level throttling at the platform layer, so production integrations should add retry-with-backoff on 429 responses. Confirm current limits with CINC support for your account.

### How do I push a lead into CINC from an AI agent through Jentic?

Run pip install jentic, then have the agent search 'create a real estate lead in CINC', load the schema for POST /leads, and execute with the lead payload. Jentic resolves the X-API-Key credential from the vault at execution time.

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

Yes. Because you run Jentic One yourself, your own rules decide which CINC operations the agent may call and which credentials it may use. Since CINC puts the lead and contact id in the URL path (`/leads/{leadId}`, `/contacts/{contactId}`), you can pin the agent to reading and updating specific records with GET and PUT while leaving out write operations like POST /leads unless you explicitly allow them. The agent can only invoke the endpoints you have scoped to it, so creating new leads or writing contacts stays off limits until you add it.