canonical: https://jentic.com/apis/commissioncrowd.com/commissioncrowd # CommissionCrowd API Jentic publishes the only available OpenAPI specification for CommissionCrowd API, keeping it validated and agent-ready. CommissionCrowd is a sales CRM aimed at independent commission-only agents and the companies that hire them. The API exposes read access to CRM core records: leads, contacts, companies, opportunities, activities, tasks, wall posts, agents, organizations, and events. Use it to mirror the CommissionCrowd pipeline into a warehouse, build reporting on agent performance, or feed an AI assistant that answers pipeline questions across the firm. ## For AI agents Read CommissionCrowd CRM data - leads, contacts, opportunities, activities, agents, and pipeline stages - through one bearer-style header key. ## Scope Does not handle creating leads, updating opportunities, or pushing data into CommissionCrowd - use for read-only CRM data extraction and reporting only. ## Capabilities - List opportunities and inspect pipeline stages via GET /opportunities/ and /lead_stages/ - Pull all leads and their current statuses for pipeline reporting - List contacts and companies with their phone numbers and email addresses - Fetch agent records and the company-to-agent assignments via /agents/ and /company_users/ - Read activity, task, and event timelines for any record - List wall posts and replies for internal conversation history ## Use cases ### Pipeline Mirror to a Warehouse Run a nightly extract that calls GET /leads/, /opportunities/, /contacts/, and /companies/ and lands the data in a warehouse table. Joining lead_stages and lead_statuses lets analysts build conversion funnels and per-agent reports outside CommissionCrowd. Read-only access keeps the source of truth intact. Example prompt: Pull the first 200 opportunities via /opportunities/ and the lead_stages list, then return a table of opportunity-by-stage counts ### Agent Performance Dashboard Combine /agents/, /opportunities/, and /activities/ to produce a per-agent dashboard: opportunities owned, activities logged, and stage progression. Useful for sales managers tracking commission-only contractor productivity without giving them direct CRM access. Example prompt: List agents via /agents/ and join with /opportunities/ to count open deals per agent over the last 30 days ### Lead Hand-off Audit When leads bounce between agents, audit the trail by joining /leads/, /lead_statuses/, /lead_stages/, and `/activities/.` The activities feed shows who touched the lead and when, so a manager can ask 'who last contacted this lead?' without scrolling through the UI. Example prompt: Get the activities list filtered by leadId 12345 and return them in chronological order ### AI Pipeline Assistant via Jentic An AI agent connected to Jentic can answer 'how many opportunities closed last week?' by searching for the right CommissionCrowd operation and executing it. Jentic stores the Authorization key in your Jentic One instance so agents work with the data without ever seeing the raw key. Example prompt: Use Jentic to search 'list opportunities in commissioncrowd', load the operation, and execute against /opportunities/ ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/leads/` | List leads | | GET | `/opportunities/` | List opportunities | | GET | `/contacts/` | List contacts | | GET | `/companies/` | List companies | | GET | `/agents/` | List agents | | GET | `/activities/` | List activities | | GET | `/lead_stages/` | List pipeline stages | | GET | `/tasks/` | List tasks | ## Key resources - **Leads and Opportunities** — Pipeline records with stages, statuses, and ownership - **Contacts and Companies** — People and organisations linked to deals - **Agents and Users** — Commission-only agents and platform users - **Activities and Tasks** — Activity timelines and to-do tasks attached to records - **Wall posts and Events** — Internal feed posts with replies and calendar events ## Why Jentic - **Setup:** Wiring CommissionCrowd by hand means learning its API key scheme, attaching the key to each CRM request, and paging through leads and opportunities yourself. Through Jentic you install once, import CommissionCrowd from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** CommissionCrowd exposes read-only CRM extraction, so limit the agent to the operations it needs, such as listing leads, opportunities, or contacts. You choose the operations it may call, so reporting reads are allowed while anything you leave out stays uncallable. - **Credential handling:** Your CommissionCrowd 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 'list open opportunities' or 'pull recent leads', and Jentic returns the matching CommissionCrowd operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Pipedrive API** — Pipedrive is a full-feature sales CRM with read and write coverage across pipelines, deals, and activities. - **Copper CRM API** — Copper is a Google Workspace-native CRM with a similar lead, opportunity, and activity model. - **Insightly API** — Insightly is a project-and-CRM hybrid covering similar lead, contact, and opportunity records. ## FAQ ### Why is there no official OpenAPI spec for CommissionCrowd API? CommissionCrowd does not publish an OpenAPI specification. Jentic generates and maintains this spec so AI agents and developers can call CommissionCrowd 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 CommissionCrowd API use? CommissionCrowd uses an API key passed in the Authorization header on every request. Through Jentic, the key is stored encrypted in your Jentic One instance and never enters the agent's context - the agent only sees the response of the operation it called. ### Can I list pipeline stages and statuses with the CommissionCrowd API? Yes. GET /lead_stages/ returns the configured pipeline stages and GET /lead_statuses/ returns the lead status values. Join these with /leads/ and /opportunities/ to produce stage-by-stage funnel reports. ### Is the CommissionCrowd API read-only? Yes. All 17 endpoints are GET - there are no documented create or update operations. Use it for reporting, mirroring, and agent-driven question answering rather than as a write surface. ### What are the rate limits for the CommissionCrowd API? CommissionCrowd does not publish a hard public rate limit. In practice, paginated extracts at a steady pace work reliably; back off on 429 responses and prefer pagination over large unfiltered list requests. ### How do I list opportunities through Jentic? Search Jentic for 'list opportunities in commissioncrowd', load the schema for GET /opportunities/, and execute. The Jentic Python SDK pattern is await client.search(...), await client.load(...), await client.execute(...). ### Can I limit what my agent is allowed to do with the CommissionCrowd API? Yes. Because Jentic One is self-hosted, you set the rules, and your instance holds the encrypted API key and injects it at execution time, so the agent never sees the raw credential. The CommissionCrowd API is read-only, so you pick exactly which operations the agent may call, such as listing leads, opportunities, or contacts, while any operation you leave out stays uncallable. This means you can allow pipeline reporting reads and keep everything else off limits.