canonical: https://jentic.com/apis/leadtributor.cloud/leadtributor # leadtributor.cloud - API The Leadtributor API distributes sales leads from a manufacturer or brand to its network of sales partners and tracks how each lead progresses with the partner it went to. A lead is created from two field lists, the prospect and their interest, and can then be commissioned directly to a sales partner and sales pipeline, or offered on a market so the platform brokers it to relevant partners. The API also lists leads filtered by commission step, responsible person, and dates, finds likely duplicate leads with a 0 to 100 match score, adds notes and attachments, invites and manages sales partners, and subscribes webhooks to platform events. ## For AI agents Create sales leads, commission them to sales partners and pipelines or offer them on a market, track commission progress, detect duplicate leads, and manage your sales partner network. ## Scope Does not handle email marketing, quoting or invoicing, partner payouts, or contact enrichment. Use for creating leads and distributing them to sales partners and markets only. ## Capabilities - Create a lead from a prospect and interest field list and commission it to a sales partner, optionally into a specific salesPipelineId - Offer a lead on a market so the platform brokers it to relevant sales partners - List leads filtered by commission.stepName, commission.responsible, commission.closedAt, or lead.createdAt, and sort by modifiedAt - Find likely duplicates of a lead with a 0 to 100 score, tuned by maxDistanceKm and minScore - Add notes to a lead, list notes across all leads modified since a date, and announce attachment uploads - Invite sales partners by email, update their tags and attributes, end the relationship, or remove them - Subscribe a webhook URL to a platform eventName and review the last 100 events sent for it ## Use cases ### Agent-run lead routing through Jentic An AI agent handling inbound enquiries can create each lead in Leadtributor, check it for duplicates, and commission it to the right sales partner. Through Jentic the agent finds each operation by intent and the Authorization header key is injected at execution time, and a rule can allow lead creation and commissioning while leaving partner deletion and webhook changes out of reach. Example prompt: Call POST /leads with the prospect and interest field lists from the web form, call GET `/leads/{leadId}/duplicates` with minScore 80, and if none are returned call POST `/leads/{leadId}/commissions` with the chosen salesPartnerId ### Partner channel lead distribution Manufacturers selling through dealers, installers, or resellers need each lead to reach a partner who can act on it. Leadtributor supports direct commissioning to a named sales partner and pipeline, and market-based brokerage where a lead is offered on a market and distributed to relevant partners. Example prompt: Call POST `/markets/{marketId}/brokerages` with the leadId of the new enquiry to offer it on the regional market ### Commission progress reporting Once leads are with partners, the brand wants to know what happened to them. Listing leads with filters on commission.stepName, commission.responsibleName, commission.startedAt, and commission.closedAt shows where each lead stands in the partner's process, and notes added by either side carry the context. Example prompt: Call GET /leads with a commission.closedAt filter for the current month and includeFieldLists true, then summarise closed leads by partner ### Sales partner network management A partner network changes as dealers join and leave. The sales partner operations invite a partner by email with optional tags and attributes, list partners by status such as ACTIVE, PENDING:INVITED, or ENDED, update their tags and attributes, and end or delete a relationship. Example prompt: Call POST /sales-partners with email 'dealer@example.com', name 'Example Solar GmbH', and tags ['bavaria'], then list partners with GET /sales-partners and status 'PENDING:INVITED' to confirm the invite ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/leads` | Create a lead | | GET | `/leads` | List leads | | POST | `/leads/{leadId}/commissions` | Commission a lead to a sales partner | | POST | `/markets/{marketId}/brokerages` | Offer a lead on a market | | GET | `/leads/{leadId}/duplicates` | Get duplicate candidates | | POST | `/sales-partners` | Invite a sales partner | | POST | `/webhooks` | Subscribe a webhook | ## Key resources - **Leads** — Create, list, get, and modify leads, commission them to partners, find duplicates, and add notes and attachments - **Markets** — Offer a lead on a market so it is brokered to relevant sales partners - **Sales partners** — Invite, list, update, end, and delete sales partners - **Webhooks** — Subscribe and unsubscribe webhooks and list recent events per event name - **Forms and notes** — List lead forms and notes across all leads ## 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:** 64 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 93 / 100 - Developer Experience & Jentic Compatibility: 56 / 100 - AI-Readiness & Agent Experience: 50 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 69 / 100 - **View full report:** https://jentic.com/apis/leadtributor.cloud/leadtributor/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 ``` ## Why Jentic - **Setup:** Wiring Leadtributor by hand means sending the key in the Authorization header, keeping production and demo hosts apart, building prospect and interest field lists with typed fields, and running the two-step attachment upload. Through Jentic you install once, import Leadtributor from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Leadtributor puts the lead, market, and sales partner ids in the URL path (`/leads/{leadId}/commissions`, `/sales-partners/{salesPartnerId}`), so a rule can pin your agent to one lead, market, or partner and the operations you pick. You choose the operations it may call, so destructive ones like deleting a sales partner or unsubscribing a webhook are not included unless you add them. - **Credential handling:** Your Leadtributor 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 'commission a lead to a sales partner' or 'find duplicate leads', and Jentic returns the matching Leadtributor operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Salesforce API** — Full CRM with leads, opportunities, and partner community features - **Pipedrive API** — Sales pipeline CRM for deals and activities - **Close CRM API** — CRM built for inside sales with calling and email - **LeadMagic API** — B2B contact and company enrichment ## FAQ ### Is there a Leadtributor MCP server? You don't need an MCP server to give your agent the Leadtributor API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it. Operations are discovered on demand, so your agent's context carries no tool definitions it will not use. ### What authentication does the Leadtributor API use? Per its OpenAPI spec, the Leadtributor API uses an API key sent in the Authorization header, declared as the apiKey scheme. The spec lists a production host and a separate demonstration platform host, so use the key that belongs to the platform you call. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected at execution time. ### Can I detect duplicate leads with the Leadtributor API? Yes. GET `/leads/{leadId}/duplicates` returns potential duplicates of a lead, each with a score from 0 for no match to 100 for an exact match and the criteria that matched, covering email, name, company, and location. Use minScore to drop weak candidates and maxDistanceKm to bound location matching. ### What are the rate limits for the Leadtributor API? The OpenAPI spec does not specify rate limits. Check https://developer.leadtributor.cloud for current limits. ### How do I send a lead to a sales partner through Jentic? Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import the Leadtributor API from the directory, and store your API key. Your agent then searches for 'commission a lead to a sales partner' and Jentic returns POST `/leads/{leadId}/commissions`, which requires salesPartnerId and accepts an optional salesPipelineId. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### How do I attach a file to a Leadtributor lead? It takes two steps. Call POST `/leads/{leadId}/attachments` to announce the upload, then send the file as a multipart/form-data POST to the uploadUrl in the response, along with the fields it returned. ### Can I limit what my agent is allowed to do with the Leadtributor API? Yes. For an intake assistant, write a rule that allows POST /leads, GET `/leads/{leadId}/duplicates`, and POST `/leads/{leadId}/notes`: the agent can create leads, check for duplicates, and add notes, but cannot commission leads, invite or delete partners, or change webhooks, and every call it makes is logged.